Hi, At a certain stage in my scripted module, I’m experiencing a crash of Slicer that occurs around 1 out of 10 times. I have no clue what’s causing it, especially since this crash leaves no trace: no popup, nothing in the Slicer log and nothing while Python remote debugging using Pycharm. I would…

We had a look at the build and it turned out that the problem was that that on that computer a debug-mode Python was listed in the PATH environment variable, which caused build system to find that unrelated Python distribution (without the required Python development files) instead of Slicer’s Pytho…

This can be tricky. Probably some operation does a non-safe memory operation but doesn’t trigger a crash until later depending on the sequence of operations. Easiest can be to look for unsafe usages by taking out pieces of functionality to see if you can isolate the cause of the crash. If that do…

Thanks for the reply Steve ! I already tried to compile Slicer in Debug mode, but I ran into the link issue with Python still being in Release ( similar issue here but with SimpleITK). Error LNK1104 cannot open file 'python36.lib' [D:\...\build\Slicer\CTK-build\PythonQt-build\PythonQt.vcxproj] Unf…

It would be great if the regular windows users could help you with the compile issue. As a rule we want to make sure that anyone who follows developer documentation should have a painless compile experience.

Many of us build Slicer in debug mode every day without problems. It is fine that Python is built in release mode and the rest of the application in debug mode. Python is built in release mode by default in Slicer (and probably in all other applications that embed Python), because we rarely need to …

I checked out yesterday’s head of the master ( 0e7423f ), left the CMake options untouched and I built into an empty folder. What’s weird is that it says it has found python36.lib in release (and python39 in debug) at the beginning of the PyhtonQt part: 43> -- Found PythonLibs: optimized;D:/dev-ext…

“D:\dev-ext\build\Slicer” - this path is too long. Please try from scratch with “D:\S4” source and “D:\S4D” binary directory.

I did exactly that and still faced the same error :slightly_frowning_face:

Debug Slicer crash from scripted module

Development

atracsys-sbt (Sylvain Bernhardt) November 19, 2021, 9:12pm 10

After temporarily renaming C:\Python to something else, it worked !

Install extensions in Slicer in Debug

Topic		Replies	Views
Build error in Windows in debug mode due to python312_d.lib Development build	9	454	August 18, 2025
Latest master does not build in Debug mode Development	7	742	April 27, 2017
How Can I debug the Module and create the personally Module? Development debug	22	1268	November 17, 2021
Problem with enabling remote debugging for both c++ and python Support	11	2051	June 2, 2017
Integrate pycharm and Slicer Support	7	2262	December 6, 2024

Debug Slicer crash from scripted module

Related topics