search

Ultimaker / Cura

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

v4.12, v4.13, v4.13.1 Application crash (not responding) #11467

Open Wobberjockey opened 2 years ago

Wobberjockey commented 2 years ago

Application Version

4.13.1

Platform

Win 10 21H2 (19044.1526)

Printer

Artillery Sidewinder x1

Reproduction steps

Install Cura set up printer using default X1 values. (just hit next through the setup process) load changes from account. wait 15 to 30 seconds.

Actual results

right click in the build volume - crash attempt to access menu - crash change slicer settings - crash load a model (any model file) - crash try to do almost anything -> crash not responding

subsequent runs of cura will immediately go to a blank white screen, not responding after "loading build volumes" issue will persist through OS restart (and even an OS update) until the application is completely uninstalled including all application date, user app data, and the application itself

clearing application is only a temporary fix

Expected results

the application should load. currently it seems like something in the sync to an ultimaker account is broken, and this process is corrupting some data preventing subsequent loads that said, issue is present even if account setup is skipped

Checklist of files to include

Additional information & file uploads

cura.log

Issue is persisting through multiple cura versions, have been able to consistently reproduce on my system after every cura clean install Chitubox has NEVER been installed on the PC in question, and version 4.12.1 worked without issue until I updated to 4.13. it no longer works, and suffers the same crash as v4.13 and 4.13.1 All cura marketplace materials and plugins have been removed from my ultimaker account on the off chance that the issue was related to something there. issue is also present when skipping the account setup step. Issue has persisted through several graphics driver updates as well

fvrmr commented 2 years ago

Hi @Wobberjockey thank you for your report. Unfortunately your log file doesn't show what is happening and I can't reproduce your issue my self. Also in the logs it shows that this has nothing to do with your Ultimaker account. Maybe this issue is related to yours? https://github.com/Ultimaker/Cura/issues/10905

Wobberjockey commented 2 years ago

That does appear to be a similar problem, yes.

I’ll test to see if there is a program running as admin in the background and see if that is the issue. (I think that was the thinking in the other thread, if I followed it properly)

I had already tested agains fusion, Vivaldi (my browser), discord, and a few other apps but there might be something else that slipped under the radar.

I do not believe I installed any other software around the time of the issue.

Wobberjockey commented 2 years ago

hopefully double posting is not against guidelines

I did some testing of the items listed in #10905

Pleas let me know if you have any other ideas for testing

one possible lead

image

putting that through process explorer nets me this

image I checked - currently installed python version is 3.8.10... might that be the cause?

edit 2: updating python to 3.9 had no change.

fvrmr commented 2 years ago

Hi @Wobberjockey do you maybe have a firewall enabled, are you using a VPN or do you have a network drive?

Wobberjockey commented 2 years ago

Using the standard windows defender firewall. Cura is already as an exception, and allowed to communicate.

There were no changes to the home modem/router that might block communication either.

no VPN.

No mapped network drives.

fvrmr commented 2 years ago

Then we have to wait for other users running into this issue, who have reproduction steps which we can reproduce. Since we can't reproduce it ourselves or see what is causing this in the log file.

Wobberjockey commented 2 years ago

Are you able to recommend any further steps I can take that might produce more data for you to work with?

Ghostkeeper commented 2 years ago

The application crashes during the creation of the main window. Unfortunately, that main window creation is done by a GUI framework we're using, Qt. It's C++ code and doesn't log exceptions very well in the release build. So there is very little we can see from the crash.

One possibility to get more information is to run Cura through a debugger, such as GDB or Visual Studio Debugger. It'll give little information since Qt is a release build, but it'll at least indicate if the problem is in Qt, in Windows, in the GPU drivers or in some other component. Explaining how to run an application through GDB is sufficiently complex though (for someone not experienced with it) that I won't attempt to do that via Github comments.

So other than that, I hope that we can find some patterns in the people who experience this issue, if we get more reports about it.

fieldOfView commented 2 years ago

Do you have multiple displays? If so, can you try running with a single display (ie: disconnect or disable the other display(s))?

Wobberjockey commented 2 years ago

YES! on PC display only mode the program runs without any issue. fired right up and complained about not being able to contact the login server.

Closing the program and re-opening it with dual displays caused the issue to reoccur instantly. More testing is required around this but it's clearly a factor - i will try playing with the graphics driver profile

Ghostkeeper commented 2 years ago

Could be looking at https://bugreports.qt.io/browse/QTBUG-47059 or https://bugreports.qt.io/browse/QTBUG-65882 here.

tvixen commented 2 years ago

I have the same issue as Wobberjockey. Also having 2 screens. I have just run ver 4.8 and 4.10 these are running fine.

fieldOfView commented 2 years ago

If Cura starts when you have all but a single screen disabled/disconnected, deselect the option to "Restore window position on start" in the General preferences. This makes sure that Cura always starts on the primary screen, which probably fixes this problem.

tvixen commented 2 years ago

4.10 seem to work until I installed Sidebar GUI plugin from Marketplace. Then it stopped responding.

fieldOfView commented 2 years ago

@tvixen I think that is merely coincidental. By default, Cura starts up in the position where you last closed it. On some systems, Cura will become "unresponsive" if it opens on the secondary screen. As long as Cura starts on the primary screen, there are probably no issues. That is what unselecting the option to "Restore window position on start" is for.

I think you "coincidentally" moved Cura 4.10 to the secondary screen, and then restarted Cura to finish installing the Sidebar GUI plugin.

Try disabling/disconnecting the second screen before opening Cura. If that works, be sure to uncheck "Restore window position on start".

tvixen commented 2 years ago

I re-installed a 4.10 from scratch and start to turn on things one by one. (but still with the plugins enabled) "Restore window position on start" did not change the responce, but it ment something to set the "Setting Visibility" to ALL. Then the laptop went crazy slow. And if I then unfold all the settings, (Infill, Material, Speed etc) then its almost not responding.

I will try this with the new version 13.1 also

(It could a laptop problem.... And I will try to install them both on another laptop)

tvixen commented 2 years ago

Installed ver 4.10 and 4.13.1 on a Dell laptop. And no problems. (Windows 8.1) Re-installed version 4.10 on a HP laptop. Coulden't run 4.10 with Sidebar GUI (Windows 10 - 21H2 ) And just did the same with 4.13.1 Totally dead (No response) with sidebar GUI. But full responsive without Sidebar GUI plugin.

Sorry fieldOfView, but thats a fact. I love your tool, but its not working smooth any more :(

tvixen commented 2 years ago

Oki, did it one more time on my HP laptop, to prove that I was wrong.

Removed 4.13.1 Installed 4.13.1 clean install with out plugins Everything was running 100% and no delays installed my plugins from Marketplace except Sidebar GUI and did a restart of Cura. Loaded a stl and sliced it. No problems.

Then I installed Sidebar GUI, and restarted. Cura Not responding :(

Deleted the profile in C:\Users\tim.milgart\AppData\Local\cura 4.13.1 and C:\Users\tim.milgart\AppData\Roaming\cura\4.13 Restarted Cure..... set it up again without Sidebar GUI.

Everything was working perfect again.

fieldOfView commented 2 years ago

Ok, then please read this issue: https://github.com/fieldOfView/Cura-SidebarGUIPlugin/issues/29#issuecomment-1041352299

Wobberjockey commented 2 years ago

If Cura starts when you have all but a single screen disabled/disconnected, deselect the option to "Restore window position on start" in the General preferences. This makes sure that Cura always starts on the primary screen, which probably fixes this problem.

This seems to fix it for me

tvixen commented 2 years ago

It didn't for me. Even with both screens off, and only the laptop screen on, Cura was not responding after startup. But when disabling the plugin it was responding again, and fast as usual. I can't test/debug Cura while the Sidebar GUI plugin is enabled, as the program just show "Not Responding" after 1min.

But the HP laptop is the only pc I have this problem on (2 others is running fine). So I don't know if its interesting for you to debug the issue, fieldOfView?