diegopradogesto
commented
6 years ago Weird, I don't see anything wrong in the logs and using your configuration folder, Cura runs without problem.
Open akf-was-here opened 6 years ago
diegopradogesto
commented
6 years ago Weird, I don't see anything wrong in the logs and using your configuration folder, Cura runs without problem.
akf-was-here
commented
6 years ago Ok, any idea what I do next? I've uninstalled / reinstalled to a new directory but the behavior doesn't change.
Thierry-CR10S-user
commented
5 years ago Hi, same thing for me. But i find why in my case: after upgrade V3.5.0 => V3.6.0 when trying to open my stl file by double click, the crash occur. When you open cura and next open your file it's OK It's because windows try to open the file why Cura 3.5 Only do "open with" on stl's file and choose the right version (careful you have 2 choices and the both why "Cura" name
akf-was-here
commented
5 years ago Seems like not really the same thing then. In my case I'm trying to directly open the Cura application (via it's own icon in it's own install directory) and it crashes where in your case that operation seems to work. I'm not spawning Cura via opening an STL which in your case seems to be crashing.
Aiddy81
commented
5 years ago I had the same issue where it wouldn't load after clicking the icon, I found it was due to an incompatibility with one of the settings from 3.5.1, on the crash window I selected backup and reset config. After doing this 3.6 loaded and I re-configured it.
akf-was-here
commented
5 years ago My crash window is a Windows 10 crash window, there isn't any option to backup and reset config.
vegar
commented
5 years ago I experience the same thing. Splashscreen shows, stops at 'Loading Interface...'. No cpu usage. Using SysInternals Process Monitor (see attached log), I can see that there is no more activity after loading some QtQuick controls.
SteeveGL
commented
5 years ago I got the same issue cause by my multi monitor setup. If I move Cura's window to a secondary monitor and click on some menu, Cura crash. When opening it again, it stuck at loading...
Workaround:
This will not happen again if the window is not move to the secondary monitor.
Be able to reproduce in:
nallath
commented
5 years ago It seems like this is an upstream bug from Qt (the graphical framework that we use).
JonS9999
commented
5 years ago Hi. I'm having similar issues: Cura 3.6.0 crashes at startup -- after the splash screen finishes, I see the Change Log window briefly, then a Windows pop-up appears and says that Cura has crashed.
I did some investigation a couple weeks ago, and it seems like it might be an issue with Python or with Qt.
Should I open a new trouble ticket, or should I chime in here since Qt was mentioned...?
-Jon
Ghostkeeper
commented
5 years ago Seems like almost everyone in this thread is experiencing this problem slightly differently :laughing:
akf-was-here
commented
5 years ago I hadn't opened my 3.6 install since my last post here (mid-Dec) but in trying steevegldev's suggested fix I found that it has "magically" fixed itself in the interim. I've gotten several windows patches since then so maybe one of them altered the behavior.
MadderPad
commented
5 years ago Just to add I got this with a box fresh Dell laptop today. Running as administrator fixed the issue.
I suspect it's connected with the screen resolution/drivers/window layout - I have a 4k screen - running as my user account, the splash screen etc is way big (as if it's reading the screen resolution incorrectly), and it crashes at "loading interfaces" as described above. Running as Admin, the splash is the right size, and then loads as normal.
Paddy
JonS9999
commented
5 years ago akf-was-here : I tried steevegldev's suggestion, but unfortunately it didn't help.
MadderPad : Interesting... I have been using Cura 4.0 BETA successfully, so I'm hesitant to go back to 3.x (if I have to for some reason, I'll try your 'run as administrator' suggestion).
kurisun
commented
5 years ago Ran into the issue on Windows 10 as well. Trying to drag the Cura 3.6 window to my other monitor and then interacting with menu options causes a Not Responding error. After closing Cura forcibly, and rebooting, the issue persists on subsequent launches. I didn't know about the Cura window fix and instead disabled my second monitor before launching Cura, which fixed the issue. I'm running the latest Nvidia drivers if that matters.
Ghostkeeper
commented
5 years ago We're not really doing anything special other than creating a window with Qt and giving it the position that the last window was closed at. I have no idea how to approach this bug... :disappointed:
digigram
commented
5 years ago @Ghostkeeper as a band-aid, maybe Uranium can be patched where it checks if the geometry is out of range, and constrain it to screen 0 only. I get this same bug any time more than 50% of the Cura window is on screen 1. Crashes consistently whether the window_left is positive or negative (i.e. screen 1 is to the left or right of screen 0). Both v3.6 and v4.1
Ghostkeeper
commented
5 years ago We don't know which screen is screen 0 though.
I think that your problem manifests itself on other computers with different screens as well. It's not necessarily related to being on screen 0 or screen 1.
To limit Cura to screen 0 would be very annoying to users with multiple screens. For instance at work I use a laptop provided by Ultimaker with a tiny screen but I practically only use the plug-in monitor with it.
JonS9999
commented
5 years ago Hi all.
I think I figured out why it's been crashing for me (I'm not saying this is everyone's reason; just mine). I hope I can explain this well enough as I haven't had my morning coffee yet today...
I have two video cards in my PC -- one built-in video card (screen 1) and a PCI-Express video card (screen 0). The PCI-Express is powerful enough to support a new enough version of Open-GL so that Cura layer-preview (sorry, not the right words -- it's the thing at the bottom of the Preview page that has a "play" button and will show you how each layer will be extruded). My built-in video card is not powerful enough to run a newer version of Open-GL, thus, it won't do the layer-preview.
By default, Cura opens on screen 0 (PCI-Express card), and life is good. But when I drag Cura to screen 0 (built-in video card), Cura crashes.
What clued me in to this was that I have an identical PC (same make & model, same amount of RAM, etc), however I don't have a PCI-Express video card in that PC -- I am only using the built-in video card. I noticed that when I run Cura on that PC, I don't see layer-preview thingie. Cura runs fine, but I just don't have the option of simulating the printing of layers.
So, that made me wonder if the problem is:
Moving the Cura window from a more powerful video card to a less powerful video card.
Moving the Cura window from one version of Open-GL to a different version of Open-GL.
Anyway, food for thought...
Cheers.
-Jon
akf-was-here
commented
5 years ago @Jon: I have two identical pci express video cards (driving 5 monitors in my setup) in a similar config as your are describing while still having issues so I don't think (for me at least) it's a more to less powerful video system as you describe in your #1 above. Mine are also both using the same drivers (I hope) so (again for me at least) that means it's not an Open-GL version difference either.
JonS9999
commented
5 years ago @jon: I have two identical pci express video cards (driving 5 monitors in my setup) in a similar config as your are describing while still having issues so I don't think (for me at least) it's a more to less powerful video system as you describe in your #1 above. Mine are also both using the same drivers (I hope) so (again for me at least) that means it's not an Open-GL version difference either.
Well, so much for my theory -- LOL. :-) :-)
-Jon
Ghostkeeper
commented
5 years ago Could you go into the preferences and enable "Force Layer View Compatibility Mode"? That should configure Cura to use OpenGL2.1-compliant shaders.
If you're unable to start Cura, you can set this setting by opening the file C:\Users\<username>\AppData\Roaming\cura\3.6\cura.cfg with a text editor. Under the category [view] you can add the following line:
force_layer_view_compatibility_mode = True
GregValiant
commented
1 week ago I'm cleaning house. Is this still a problem with current Cura versions (5.8.0 and up)? Can I close this?
Application Version
3.6.0
Platform
Windows 10 64bit
Printer
None, won't load at all
Steps to Reproduce
Start the program. Looks like it's bombing out at "Loading Interfaces".
Actual Results
Windows message "Cura.exe has stopped working"
Expected results
Program shouldn't crash.
Additional Information
cura.log:
3.6.zip