"Application has run out of memory"

Support
1

Operating system: Microsoft Windows
Slicer version: 5.8.1
Expected behavior: File saving when “Save” is pressed; able to edit/mark scene
Actual behavior: On four different normally working computers, an error message appears reading “Slicer has caught an application error, please save your work and restart.
The application has run out of memory. Increasing virtual memory size in system settings or adding more RAM may fix this issue.
If you have a repeatable sequence of steps that causes this message, please report the issue following instructions available at https://slicer.org
The message detail is:
Exception thrown in event: bad allocation” when anything is clicked. Computers have been restarted, I have made sure I have enough available RAM, and this has been occurring over multiple weeks when this was not an issue before. Any help would be greatly appreciated!

2

What are you actually trying to save? To get specific help, please provide the steps you followed and what data you are using.

3

I don’t come from a tech background so hopefully this is the right information. I have a series of several thousand pictures from micro-CT scans of sea slugs and I’m tracking organ regeneration using this. My “volume” is saved as an MHA file, and the current organ system/segmentation I’m working on is saved as an NRRD file. Currently, I have the above error message when saving (“Save Data” and selecting my desired folder) and when trying to mark the organs in the digestive system (“Segment Editor” and “Paint”). I do not have any issue loading the data. Thank you in advance!

4

Okay, yes, that’s helpful info. As the error message says, the program detects that it doesn’t have enough memory to complete the task. It’s possible this is an error, perhaps due to something unique to the data you have or the way you are using it.

The easiest thing is to try a bigger computer and see if you are really running out of memory.

If the issue happens consistently or is otherwise unsolved, it would help for you to share the exact procedure, ideally with data leads to the problem. If you can’t share the data, you can try to replicate the issue using data that is already public.

5

You may want to run your data on MorphoCloud where there is ample memory. See the instructions at https://instances.morpho.cloud