Slicer crashes on Show3D in SegmentEditor

Hello,

I’m using Slicer to segment single slices (not all) of a biological microCT sample. Unfortunately, after a while, I guess when the segmentation has reached a certain size, Slicer crashes with the error: “slicerApp-real.exe has stopped working”. I noticed that this error only occurs, if I have the segmented slices plotted in 3D. When I do the segmentation without having activated “show 3D” in Segment editor, I do not face this issue. Furthermore, if I later on try to activate “Show 3D”, slicer crashes immediately most of the times.

Also when I load the segmentation without a stack, slicer crashes upon “show 3D”. I faced this issue on two machines, both with the latest slicer version installed and quite a lot of RAM (64 GB), furthermore, I have another segmentation of that size, that also elicits the same behaviour. Therefore I suspect it is independent of the machine, probably dependent on the files, but these have been fully created in Slicer. The final segmentation (XYZ.seg.nrrd) is about 11 MB. It comprises a segmentation on about 50 of 2388 slices, so on average every 40th to 50th slice is labeled with 2 Segments. If it helps, I can send or upload one of the segmentations that cause the error.
In the following the log file of the session in which I loaded the segmentation and slicer crashed upon show3D in segment editor.

Many thanks for your work on slicer so far and thanks in advance for your help.
Martin

[DEBUG][Qt] 08.07.2020 17:05:55 [] (unknown:0) - Session start time …: 2020-07-08 17:05:55
[DEBUG][Qt] 08.07.2020 17:05:55 [] (unknown:0) - Slicer version …: 4.10.2 (revision 28257) win-amd64 - installed release
[DEBUG][Qt] 08.07.2020 17:05:55 [] (unknown:0) - Operating system …: Windows / Professional / (Build 9200) - 64-bit
[DEBUG][Qt] 08.07.2020 17:05:55 [] (unknown:0) - Memory …: 65495 MB physical, 76759 MB virtual
[DEBUG][Qt] 08.07.2020 17:05:55 [] (unknown:0) - CPU …: GenuineIntel , 8 cores, 8 logical processors
[DEBUG][Qt] 08.07.2020 17:05:55 [] (unknown:0) - VTK configuration …: OpenGL2 rendering, TBB threading
[DEBUG][Qt] 08.07.2020 17:05:55 [] (unknown:0) - Developer mode enabled …: no
[DEBUG][Qt] 08.07.2020 17:05:55 [] (unknown:0) - Prefer executable CLI …: yes
[DEBUG][Qt] 08.07.2020 17:05:55 [] (unknown:0) - Additional module paths …: (none)
[DEBUG][Python] 08.07.2020 17:06:00 [Python] (C:\Program Files\Slicer 4.10.2\lib\Slicer-4.10\qt-scripted-modules\SubjectHierarchyPlugins\AbstractScriptedSubjectHierarchyPlugin.py:36) - Scripted subject hierarchy plugin registered: Annotations
[DEBUG][Python] 08.07.2020 17:06:01 [Python] (C:\Program Files\Slicer 4.10.2\lib\Slicer-4.10\qt-scripted-modules\SubjectHierarchyPlugins\AbstractScriptedSubjectHierarchyPlugin.py:36) - Scripted subject hierarchy plugin registered: SegmentEditor
[DEBUG][Python] 08.07.2020 17:06:01 [Python] (C:\Program Files\Slicer 4.10.2\lib\Slicer-4.10\qt-scripted-modules\SubjectHierarchyPlugins\AbstractScriptedSubjectHierarchyPlugin.py:36) - Scripted subject hierarchy plugin registered: SegmentStatistics
[DEBUG][Qt] 08.07.2020 17:06:01 [] (unknown:0) - Switch to module: “Welcome”
[DEBUG][Qt] 08.07.2020 17:09:00 [] (unknown:0) - “Segmentation” Reader has successfully read the file “G:/xxxxxx/xxxxx/xxxxx/xxxx/xxxxx/200707/Segmentation_200707_1716.seg.nrrd” “[35.60s]”
[DEBUG][Qt] 08.07.2020 17:09:34 [] (unknown:0) - Switch to module: “SegmentEditor”

Please try the latest Slicer Preview Release has errors, too. If yes, then please share the segmentation file so that we can debug.

1 Like

Installing and using the latest Preview release totally solved that issue. Thanks for your help! And sorry for bothering you with that. I could have tried that myself…

1 Like