Slicer version :5.0.2
Operating System :Microsoft Windows 10
3D Slicer shut downs suddenly when cropping a hollowed model from DICOM data ,
Starting by a threshhold selection, then hollowing the model , the first crop can be done, then 3D slicer shut downs if I try a second one .
Most likely you have run out of memory. What is the size of your data set? In your system information, what are the “Total physical memory” and “Total virtual memory” values?
You can go to Volumes module and copy here these values from the Volume information section for all the volumes:
Image Dimensions
Number of scalars
Scalar type
Have you changed the geometry of your segmentation (set an oversampling value of >1)?
While you are editing your segmentation how much physical memory and virtual memory still available?
Can you describe the list of steps that leads to the application crashing? If possible, use one of the sample data sets, so that we can reproduce what you do without the need to get your data.
I just ran into this problem - shutdown during segment editing - and the culprit was indeed memory size.
I was monitoring the RAM usage and it never went above 70%, however I guess Slicer hit the limit before the monitoring could report 99% or similar.
Today I added 16 GB to the existing 16 GB and everything works like a charm. Actually, memory usage never seems to exceed 50%, but I guess there are short peak usages that just go unreported and this can cause the crashes.
I wish Slicer could somehow be able to react to the impossibility to allocate memory, but I understand it may not be straightforward. I wonder why the system did not start to swap, although the performance would probably not have been that great…
Often the memory allocation errors come from the VTK layer that Slicer uses. More information in this thread. If you are working with bigger data, of course save often, but also use the rule of thumb that you need about RAM or virtual memory about 10x the size of your data volumes.