search

Ultimaker / Cura

3D printer / slicing GUI built on top of the Uranium framework
GNU Lesser General Public License v3.0
6.21k stars 2.08k forks source link

Cura crash - fresh install allows one time file open then crashes on each subsequent file open #9118

Closed pab9776 closed 3 years ago

pab9776 commented 3 years ago

Application version 4.8.0 (same results with 4.3 - 4.5.0 - 4.6.1 - 4.7.0 - 4.7.1)

Platform Windows 10 Pro 64 bit on a Lenovo ThinkPad W541 with 32GB of ram Intell(R) HD Graphics-4600 and NVIDIA Quadro KM1100M display adapters

Printer Creality Ender-3 Pro

Reproduction steps I un-installed Cura - searched the registry for ("cura" and "ultimaker") and deleted every registry entry I found - deleted every file related cura. cleaned the registry - rebooted and cleaned the registry again - re-install Cura

Screenshot(s) CuraCrash

Actual results First time open can open an stl file - when part is deleted and new part opened - Cura crashes

Expected results I should be able to run Cura - open .stl file - delete .stl file and load another one.

Log file cura.log

Additional information

fvrmr commented 3 years ago

Does it happen with every other file or just a specific file?

pab9776 commented 3 years ago

Any file. The results are the same. I get 1 load on freshly installed Cura and the second one bombs.

Ghostkeeper commented 3 years ago

The log file indicates nothing in this case. It ends without any mention of the second file being loaded, which shows that CPython crashed. And by the looks of that screenshot, it's not a normal Cura crash but a segfault in one of Cura's dependencies.

I wouldn't know how to start debugging this, unless we're able to reproduce this ourselves. But since none of the developers has seen this so far, it seems to be specific to your platform. Perhaps your GPUs?

One thing you could try is to disconnect any external monitors. If your monitors are rendered with different GPUs (one with your Intel chip and the other one with your NVidia card), Qt is known to crash when moving to the other screen than the one it started on. Perhaps the second object is causing a pop-up to appear. STLs shouldn't create pop-ups though; only images and 3MF files afaik.