Hi, Was wondering if anyone could help me! I am trying to segment a frog skeleton. Once I have used threshold and want to view the 3d image it crashes. I have everything closed except for slicer and I suspect it might be something to do with my laptops capabilities. My specs are Intel Core I7 - 975…

How big is your dataset? Can you post the log file from the Help->Report a bug and then choose the session log that crash occured (usually the one below the latest).

Hi, The file is 6.7gb and I copied everything except for the welcome. Hopefully I have copied everything correctly. Thank you! [DEBUG][Qt] 09.03.2020 16:17:43 [] (unknown:0) - Session start time …: 2020-03-09 16:17:43 [DEBUG][Qt] 09.03.2020 16:17:43 [] (unknown:0) - Slicer version …: 4.10.2 (re…

I don’t see an error message in here. Few suggestions: You re using the stable, try a preview build and see if you still have problems. We typically suggest 6-10X more memory than your dataset for segmentation tasks. Given the size of the dataset, you might be running out of memory. You can try do…

Please send the log of the session where the crash occurred. In Help / Report a bug dialog, there is a list where you can select previous sessions.

Thank you Murat! I changed the settings in Nvidia control panel and changed to the preview build. That seemed to fix the problem!!

The suggestions given to me by Murat worked. Would you still like the report? Cheers

If it’s not too much trouble, then it would be interesting how the error shows up in the log (we might then identify the problem easier next time, only by looking at the logs).

Not a problem! I believe this is the one from yesterday. [DEBUG][Qt] 09.03.2020 16:00:22 [] (unknown:0) - Session start time …: 2020-03-09 16:00:22 [DEBUG][Qt] 09.03.2020 16:00:22 [] (unknown:0) - Slicer version …: 4.10.2 (revision 28257) win-amd64 - installed release [DEBUG][Qt] 09.03.2020 16:00…

Thank you. There does not seem to be any suspicious in this log. If you are sure that this was the session where you had problems then maybe our logs were just not detailed enough to capture more information about the issue.

If this was caused by opengl crash, I never managed to get any errors on windows during my tests with 4.10.2.

Show 3D crashing after threshold

Support

lassoan (Andras Lasso) March 10, 2020, 1:17pm 12

By OpenGL crash, do you mean TDR related errors or others? How did you know that it was OpenGL crash (from displayed error message, Windows logs, …)?

Topic		Replies	Views
Unexpected error forces Slicer to shut-down Support	21	1587	August 16, 2019
volume rendering in 3dslicer Support	15	1079	June 20, 2019
M3 Pro catastrophic crash in volume rendering Support volume-rendering	12	306	October 2, 2024
Can't save the scene and the segmentations - allocation ERROR, results undefined Support	18	883	July 29, 2019
Slicer 5.10 crashes when Ctrl + click-and-drag adjusts segment opacity Support	7	57	April 28, 2026

Show 3D crashing after threshold

Related topics