fatal runtime error: out of memory

[Libbum]

Not too sure who is calling this, but if we look at pushing boundaries and calculate a grid of 1500x1500x1500, we hit the above error sometime during the run. RAM usage was close to 100GB: so within tolerance and was within the final stage where we don't see peaks in lower resolution runs.

I've done no debugging on this and will treat it as low priority, but once the system is fully operational this will need to be investigated. It's obviously in an external c library as it's not a rust panic, but which I am unsure of at present.

[Libbum]

This seems to be happening even with 50x50x50 calls now. Randomly, but more than once, so it may need to be given a higher priority.

[Libbum]

The indicatif memory issue is (hopefully) fixed in e260a02. If the estimate was negative we'd get a percentage value above 100, then feed that into a ProgressBar of size 100. There really should be a check on that, but seems there isn't will look at a pull request when I have the time.