I keep getting the error shown in the attached pic.
Slicer will stop working and eventually will shut down.
What could be causing this behavior?
It seems that the attachment did not come through. Could you please try to upload the image again?
Applications typically crash when you run out of memory. How much RAM do you have in your computer and how large is the image that you are working with?
Hello.
Here is the attachment.
The project I am working on has a size of 3GB. The installed RAM is 56GB.
I have also increased the cache size to 100GB.
The program was working properly for a long time. It started crashing during my last operations.
Thanks for your help. Regards
What effects did you use? Could you attach the application log of the session where the crash occurred? (menu: Help/Report a bug)
Hi Andras,
I was using the “Paint” effect with a radius of “1%”. You can see from the attached screenshot.
Here is the application log:
Log is not attached.
I am sorry about that.
I tried once more to repeat the operations and I had the same problem.
Here is the log file
(Attachment Slicer_28257_20190807_155407.log is missing)
Hi there,
I receive an error that some attachments are not sent.
I resent the log file as a txt file
(Attachment Slicer_28257_20190807_155407.txt is missing)
Same error,
I enclose the log file within my email:
[DEBUG][Qt] 07.08.2019 15:54:08 [] (unknown:0) - Session start time …: 2019-08-07 15:54:08
[DEBUG][Qt] 07.08.2019 15:54:08 [] (unknown:0) - Slicer version …: 4.10.2 (revision 28257) win-amd64 - installed release
[DEBUG][Qt] 07.08.2019 15:54:08 [] (unknown:0) - Operating system …: Windows / 7 / Service Pack 1 (Build 7601) - 64-bit
[DEBUG][Qt] 07.08.2019 15:54:08 [] (unknown:0) - Memory …: 57296 MB physical, 114607 MB virtual
[DEBUG][Qt] 07.08.2019 15:54:08 [] (unknown:0) - CPU …: GenuineIntel , 8 cores, 8 logical processors
[DEBUG][Qt] 07.08.2019 15:54:08 [] (unknown:0) - VTK configuration …: OpenGL2 rendering, TBB threading
[DEBUG][Qt] 07.08.2019 15:54:08 [] (unknown:0) - Developer mode enabled …: no
[DEBUG][Qt] 07.08.2019 15:54:08 [] (unknown:0) - Prefer executable CLI …: yes
[DEBUG][Qt] 07.08.2019 15:54:08 [] (unknown:0) - Additional module paths …: C:/Users/DF/AppData/Roaming/NA-MIC/Extensions-28257/SegmentEditorExtraEffects/lib/Slicer-4.10/qt-scripted-modules, C:/Users/DF/AppData/Roaming/NA-MIC/Extensions-28257/MarkupsToModel/lib/Slicer-4.10/qt-loadable-modules
[DEBUG][Python] 07.08.2019 15:54:34 [Python] (E:\Slicer 4.10.2\lib\Slicer-4.10\qt-scripted-modules\SubjectHierarchyPlugins\AbstractScriptedSubjectHierarchyPlugin.py:36) - Scripted subject hierarchy plugin registered: Annotations
[DEBUG][Python] 07.08.2019 15:54:36 [Python] (E:\Slicer 4.10.2\lib\Slicer-4.10\qt-scripted-modules\SubjectHierarchyPlugins\AbstractScriptedSubjectHierarchyPlugin.py:36) - Scripted subject hierarchy plugin registered: SegmentEditor
[DEBUG][Python] 07.08.2019 15:54:36 [Python] (E:\Slicer 4.10.2\lib\Slicer-4.10\qt-scripted-modules\SubjectHierarchyPlugins\AbstractScriptedSubjectHierarchyPlugin.py:36) - Scripted subject hierarchy plugin registered: SegmentStatistics
[DEBUG][Qt] 07.08.2019 15:54:37 [] (unknown:0) - Switch to module: “Welcome”
This is the log of the current session. Please choose the log of the session where the crash occurred (in the “Report a bug…” dialog there is a listbox to select the session).
Hi Andras,
I think it is this one:
[DEBUG][Qt] 07.08.2019 12:01:12 [] (unknown:0) - Session start time …: 2019-08-07 12:01:12
[DEBUG][Qt] 07.08.2019 12:01:12 [] (unknown:0) - Slicer version …: 4.11.0-2019-07-01 (revision 28354) win-amd64 - installed release
[DEBUG][Qt] 07.08.2019 12:01:12 [] (unknown:0) - Operating system …: Windows / 7 / Service Pack 1 (Build 7601) - 64-bit
[DEBUG][Qt] 07.08.2019 12:01:12 [] (unknown:0) - Memory …: 57296 MB physical, 114607 MB virtual
[DEBUG][Qt] 07.08.2019 12:01:12 [] (unknown:0) - CPU …: GenuineIntel , 8 cores, 8 logical processors
[DEBUG][Qt] 07.08.2019 12:01:12 [] (unknown:0) - VTK configuration …: OpenGL2 rendering, TBB threading
[DEBUG][Qt] 07.08.2019 12:01:12 [] (unknown:0) - Qt configuration …: version 5.10.1, with SSL, requested OpenGL 3.2 (compatibility profile)
[DEBUG][Qt] 07.08.2019 12:01:12 [] (unknown:0) - Developer mode enabled …: no
[DEBUG][Qt] 07.08.2019 12:01:12 [] (unknown:0) - Prefer executable CLI …: yes
[DEBUG][Qt] 07.08.2019 12:01:12 [] (unknown:0) - Additional module paths …: C:/Users/DF/AppData/Roaming/NA-MIC/Extensions-28354/MarkupsToModel/lib/Slicer-4.11/qt-loadable-modules, C:/Users/DF/AppData/Roaming/NA-MIC/Extensions-28354/SegmentEditorExtraEffects/lib/Slicer-4.11/qt-scripted-modules, C:/Users/DF/AppData/Roaming/NA-MIC/Extensions-28354/SegmentMesher/lib/Slicer-4.11/qt-scripted-modules
[DEBUG][Python] 07.08.2019 12:01:14 [Python] (C:\Users\DF\AppData\Local\NA-MIC\Slicer 4.11.0-2019-07-01\lib\Slicer-4.11\qt-scripted-modules\SubjectHierarchyPlugins\AbstractScriptedSubjectHierarchyPlugin.py:36) - Scripted subject hierarchy plugin registered: Annotations
[DEBUG][Python] 07.08.2019 12:01:14 [Python] (C:\Users\DF\AppData\Local\NA-MIC\Slicer 4.11.0-2019-07-01\lib\Slicer-4.11\qt-scripted-modules\SubjectHierarchyPlugins\AbstractScriptedSubjectHierarchyPlugin.py:36) - Scripted subject hierarchy plugin registered: SegmentEditor
[DEBUG][Python] 07.08.2019 12:01:14 [Python] (C:\Users\DF\AppData\Local\NA-MIC\Slicer 4.11.0-2019-07-01\lib\Slicer-4.11\qt-scripted-modules\SubjectHierarchyPlugins\AbstractScriptedSubjectHierarchyPlugin.py:36) - Scripted subject hierarchy plugin registered: SegmentStatistics
[DEBUG][Qt] 07.08.2019 12:01:15 [] (unknown:0) - Switch to module: “Welcome”
[INFO][VTK] 07.08.2019 12:02:20 [vtkMRMLVolumeArchetypeStorageNode (00000000144FD280)] (D:\D\P\Slicer-0\Libs\MRML\Core\vtkMRMLVolumeArchetypeStorageNode.cxx:464) - Loaded volume from file: E:/0-Hiro_Archive/GP_2016/GP_CUT_BULLA_100%_IKI_2.7um_Al/3D_Slicer_GP_CUT_BULLA_100%_IKI_2.7um_Al_REC_d2c3_working/GP_CUT_BULLA_100%_IKI_2.7um_Al_REC_d2c3.nrrd. Dimensions: 1286x1240x1872. Number of components: 1. Pixel type: unsigned char.
[INFO][VTK] 07.08.2019 12:04:46 [vtkMRMLVolumeArchetypeStorageNode (00000000144FD460)] (D:\D\P\Slicer-0\Libs\MRML\Core\vtkMRMLVolumeArchetypeStorageNode.cxx:464) - Loaded volume from file: E:/0-Hiro_Archive/GP_2016/GP_CUT_BULLA_100%_IKI_2.7um_Al/3D_Slicer_GP_CUT_BULLA_100%_IKI_2.7um_Al_REC_d2c3_working/Segmentation-label.nrrd. Dimensions: 1286x1240x1872. Number of components: 1. Pixel type: short.
[DEBUG][Qt] 07.08.2019 12:04:49 [] (unknown:0) - “MRML Scene” Reader has successfully read the file “E:/0-Hiro_Archive/GP_2016/GP_CUT_BULLA_100%_IKI_2.7um_Al/3D_Slicer_GP_CUT_BULLA_100%_IKI_2.7um_Al_REC_d2c3_working/2019-07-26-Scene.mrml” “[178.57s]”
[DEBUG][Qt] 07.08.2019 12:10:42 [] (unknown:0) - Switch to module: “”
It doesn’t seem to be the correct log either. “Switch to module:” lines indicate that you did not switch to Segment editor module in this session.
Hi,
Slicer used to crash with me as well when using the scissors tool after applying the threshold,
the file size I’m working on was around 5 GB, and I’m working on a really good computer…
I overcame this issue by:
- reducing the size of the data by using Image J (5 Gb to ~200000 KB) by reducing the pixels to one third.
- cropping the exact area I wanted to segment with safety margins using (crop volume) in 3d Slicer.
Finally, try to turn off the (show 3d) option when your segmenting.
Regards,
Raid
Hi
Another option is that Slicer has not finished a write operation.
For some of my files it was crashing as soon as I attempted to do anything after changing a volume (crop module). I got around the error by manually saving and opening a file explorer window to the save folder. If I attemtped to do anything in the Segment Editor module before the file write was complete I’d get a crash.
It may not solve your problem, but it is worth trying.
David
@dfafalis @Raid @justdcinaus I would be nice to replicate and find the specific cause of the crash, especially if it is not related to the lack memory resources on the computer.
For example, we had a similar crashing issue with large segmentation, and turned out to be a variable type that needs to be changed (Segmentation effects crashing Slicer), and is now fixed in preview version.
It would be great if you can provide datasets and the exact steps that replicate the issue.
1 Like
Hi Murat,
Thank you for your reply.
I will try to get it for you.
Best
Dimitrios
Hello Murat and Andras,
I summarize here some problems I have been encountering while using 3D Slicer.
I hope they will give you an insight of what may be going wrong.
The
problems I describe happen quite often, repeatedly, and it is frustrating to see that at the end the work I had done is not saved.
For the problems I describe in the sequence, I used a PC (windows 10 Enterprise), 3D Slicer version 4.10.2 (the latest stable).
The PC I am using has 32 GB RAM, Intel(R) Xeon(R) W-2133 CPU @ 3.60Hz 3.60Hz
Available space on SSD hard drive: 261GB
A. Screenshots Slicer_Error_3ab :
Here, screenshot a, I tried to use the Paint effect in the regions shown by yellow arrows. Slicer returned the error message shown in screenshot screenshot b.
B. Screenshots Slicer_Error_3cd:
I Continued working on the same region as in previous screenshot:
After
the Paint effect failed, I tried the Draw effect, screenshot c . The first time, after
waiting for a while for Slicer to complete its process, the effect showed nothing. So I tried for a second time and then it worked as shown
in screenshot screenshot d.
C. Screenshot Slicer_Error_3e:
Many times, I observe this strange random positioning of circles when I want to use the Paint effect.
When this happens I have to either “Esc” and use another effect, or if I need to use the Paint effect, then I just let it do whatever and then I “Undo” and repeat the process.
@dfafalis This appears to be a similar issue that was discussed in the following thread:
This was solved by a recent fix to one of Slicer’s dependencies as detailed in the linked thread. If you are working with a large data set, please try a Slicer preview release (https://download.slicer.org/) to see if this solves your problem.
@dfafalis
Yes, please try the same steps with the latest preview (after installing segmenteditorextraeffects) and see whether you still get the same error. Bad allocation error message in your first window means it is running out of memory.
