search

Ultimaker / Cura

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

5.2.1 freezes when trying to open the application #13820

Open Krominicon opened 1 year ago

Krominicon commented 1 year ago

Application Version

5.2.1

Platform

windows 11

Printer

anycubic kobra max

Reproduction steps

reopen cura from my start menu

Actual results

cura freezes on a white screen and becomes unresponsive.

Expected results

cura should open normally so i can slice files for my printer.

Checklist of files to include

Additional information & file uploads

cura.log

i found a fix on reddit where you go into the cura config file and delete the window_left, window_right, or window_top parameters under the general section and it lets me reopen cura just fine. but then as soon as i close cura again and reopen it starts all over.

MariMakes commented 1 year ago

Hey @Krominicon,

Thanks for your report 👍 Sorry, it took us a while to get back to you 😞

Could this be a duplicate of https://github.com/Ultimaker/Cura/issues/8892 ?

One of the users posted the following workaround FIXED IT BY STOPPING ASUS GPU TWEAK SOFTWARE THAT CAME WITH MY TUF 3060TI! Even though Cura ran perfectly on the same machine with the same software a few days ago...

Is this something that would work for you?

Krominicon commented 1 year ago

i don't have an asus device, i'm on an Alienware M15 R5 and the only gpu related software i have are my drivers. but yeah #8892 is a very similar, if not the same issue.

MariMakes commented 1 year ago

Hey @Krominicon,

I'm seeing similar reports of slowness and freezing for Windows 11 users. I'll start bundling them under your issue so we can keep track of them. I'll be upgrading to windows 11 myself to see if I can recreate it and bring it up to the team to see if they can see what's going on.

j-snijder commented 1 year ago

After loading a 3mf project file in which an Ultimaker dual extractor printer is used (should not be of any problem but still) now Cura wil only load, opens ALL setting panels and became totally irresponsive, nothing work anymore and Cura freeze whatever I try. What is going on here guys ? is Cura to be fixed or must we leave and abandone it ?

j-snijder commented 1 year ago

What did I do now ? After fully freezing I deinstalled all cura, really all and let Revo remove everything. Then reinstalled v 5.1.0, which I knew was working fine. I discovered I forgot installing v 5.1.1 so I did, BAMMMM Now the problems started again and cura freezes at adding custom filament.

Could it be that the newly added printers (Ultimaker) are causing the problems ?

Please investigate, I hope I accidentally discovered the problem.

MariMakes commented 1 year ago

We've added a ticket to the backlog with the intent to improve this. For internal reference CURA-9977

Thanks for the report! 👍

j-snijder commented 1 year ago

Here's my logfile, take a special look at the end, I think I discovered tht cura is looking for printers that I do not have and fails on it ?

Cura is still veryveryvery slow and unworkable, still I'm trying to clean the installed cura up as clean as I can to get back to a virgin version/fresh install.

I have to go about it this way because cura keeps on loading backups and/or data from somewhere I can't find out (yet)

cura.log

MariMakes commented 1 year ago

Hey All,

We are still trying to learn what is slowing down some Windows 11 and not others. One solution direction we are exploring is printing over USB.

Another suggestion I got is to start collecting more extensive logs. To learn better about what's slowing your software down, could you install a plug-in that performs more extensive logging?

You can download it here: https://marketplace.ultimaker.com/app/cura/plugins/UltimakerPackages/ExtensiveSupportLogging After it's installed can you....

  1. Select Extensions
  2. Select Remote Support
  3. Start CPU profiler
  4. Repeat your steps to reproduce.
  5. Stop CPU profiler
  6. Select Save Remote Support Archive
  7. Go to the Marketplace
  8. Select the gear icon
  9. Uninstall Startup Optimiser
  10. Share the Remote Support Archive Zip file here on Github

You'll need to open Github in your browser to attach any files to your ticket You can click the view it on GitHub link at the bottom of your email to open GitHub in the browser.

Thank you 🙏

zhaoyuheng200 commented 1 year ago

I manage my cura installation via chocolatey, currently running 5.2.1 I found 2 previous versions in the Roaming/cura/ folder, and it takes time to delete them. After removing all the fils in Roaming folder and re-install cura from choco install cura-new, the slowness is visibly improved. It feels like the slowness is tied to one or many of the plugins. After I restore backup and all the plugins are back, it feels slow again.

fieldOfView commented 1 year ago

In the logs provided by @j-snijder, I see that they use the Sidebar GUI plugin. You may want to try if disabling that plugin helps. There is a - somewhat elusive - issue whith that plugin that is possibly related to Powertoys FancyZone.

See https://github.com/fieldOfView/Cura-SidebarGUIPlugin/issues/29 for more information.

zhaoyuheng200 commented 1 year ago

@fieldOfView thank you! Can confirm disabling FancyZones from Powertoys alone made a significant difference in Cura 5.2.1 slowness issue.

Edit: I have Sidebar GUI installed.

Edit: Confirm removing the SidebarGUI and enable FancyZone also solve the issue. So there is definitely issue between that two softwares.

j-snijder commented 1 year ago

Hi y'all As I do not have powertoys installed I did a reinstall of cura 5.2.1, as I completely removed it because of the uselessnes for me at this moment. After installing I opened cura to try and remove the sidebar GUi plugin, and as soon as I even clicked on the market place knob cura froze and locked up totally. I' ll try it again asap but for me the powertoys issue dors not play any role in this. I'll install the detailed data gathering plugin as soon as cura lets me, but that can take a while right now because of the constantly freezing.

j-snijder commented 1 year ago

After re-reading this complete post I see that this is placed in "backlog" ? Does this mean you are putting it away in a dark corner somewhere and hope it solves itself somehow ? I hope not, and really hope you will address this cura problem seriously? If you no longer active on this, then there is no need for us to test and send you information, is there ?

MariMakes commented 1 year ago

Hey @j-snijder,

The label indicates that we've added a ticket to the backlog with the intent to improve this.
We want to fix this soon, especially since we've seen a significant amount of reports.

Troubleshooting the issue is hard since we cannot reproduce it in-house. That means that we are looking for a trend in the logs that have been provided.

Having access to extensive logging as mentioned here could improve the chance of us finding what's causing the slowdowns.

j-snijder commented 1 year ago

Okay, thanks for this explaination.

New testing result here.

I just reinstalled cura 5.2.1 and immediately found that there is a significant speed improvement after I uninstalled the Sidebar GUI plugin from ...drumroll... Cura V 5.1.1 ? HUH ? How can that be of any influence ??

Then after concluding that I switched to the dark theme and speed improved even more and is now (for the time beeing ? ) back tyo waht you may expect from Cura.

Now I am able to remove some of the less or lesser used plugins and hopefully am able to use v 5.2.1 as I am used to with previous version, why ? Just because I love Cura :)

I'll post my findings whenever I get the chance and keep you informed.

j-snijder commented 1 year ago

Hi :)

Now before someone gets the idea that I am accusing anyone of anything I want to clearly state that I am not !

As I removed the Sidebar Gui plugin and looked for anything that could be a common cause I discovered that I have removed all but one plugin from 5axes and had an idea.

I removed all plugins from 5axes and with that I discovered that the speed now is back to normal, so....

My question now is... could it be that one (or more) of the plugins by 5axes could be causing a problem with windows ?? Sidebar GUI did so what if ? could it be an unnoticed (small but anyway) thingy in one of 5axes plugins ?? could it be that one thing led to another without 5axes even knowing this ??

Anyway I'll keep on testing as I am also curious whats going on here ;)

AubsUK commented 1 year ago

POTENTIAL FINDING? - Unable to access NVIDIA OpenGL Driver from Registry

Is anyone affected NOT using NVIDIA GPU?

I'm having the same issue on Win11. This appears to have started after I updated my chipset (Asus) and rebooted. I think it corrupted something somewhere because I just told it to restart and Cura was open at the time.

That was on 5.2.1. I updated to 5.3.0 and the issue has followed me.

I can launch it as Administrator and it works fine (but I don't get my network drives where I save files).

Deleting (renaming) the "C:\Users\user\AppData\Roaming\cura" folder seems to fix it, until something crashes, and it now white-screens again, then back to the drawing board.

After deleting the folder, it can crash (white-screen) when I open 'Manage profiles' or 'Marketplace' or any other popup, and then back to the not working at all again until the next delete.

What I have noticed, if I run Cura as Administrator, everything works perfectly, 100%. My account is a local administrator, but only when elevated through UAC. @MariMakes Do the developers have UAC enabled? - If not, perhaps that's why they are able to work perfectly and not replicate the issue.

Running Process Monitor, I can see the following entries that appear when it won't run which don't appear in a successful run (Run as Administrator):

Time of Day Process Name PID Operation Path Result Detail
17:22:43.7 UltiMaker-Cura.exe 33600 RegOpenKey HKLM\System\CurrentControlSet\Services\WinSock2\Parameters ACCESS DENIED Desired Access: All Access
17:22:45.0 UltiMaker-Cura.exe 33600 RegCreateKey HKLM\System\CurrentControlSet\Services\EventLog\Application\NVIDIA OpenGL Driver ACCESS DENIED Desired Access: Write
17:22:45.0 UltiMaker-Cura.exe 33600 RegCreateKey HKLM\System\CurrentControlSet\Services\EventLog\Application\NVIDIA OpenGL Driver ACCESS DENIED Desired Access: Write
17:22:45.6 UltiMaker-Cura.exe 33600 RegOpenKey HKLM\System\CurrentControlSet\Services\WinSock2\Parameters ACCESS DENIED Desired Access: All Access
17:22:46.1 CuraEngine.exe 336 RegOpenKey HKLM\System\CurrentControlSet\Services\WinSock2\Parameters ACCESS DENIED Desired Access: All Access
17:22:49.6 UltiMaker-Cura.exe 33600 NotifyChangeDirectory C:\Program Files\UltiMaker Cura 5.3.0\share\cura\resources\meshes CANCELLED Filter: FILE_NOTIFY_CHANGE_FILE_NAME, FILE_NOTIFY_CHANGE_DIR_NAME, FILE_NOTIFY_CHANGE_ATTRIBUTES, FILE_NOTIFY_CHANGE_SIZE, FILE_NOTIFY_CHANGE_LAST_WRITE, FILE_NOTIFY_CHANGE_SECURITY
17:22:49.6 UltiMaker-Cura.exe 33600 FileSystemControl \My_Server_UNC\Path\ NOT REPARSE POINT Control: FSCTL_GET_REPARSE_POINT
17:22:54.6 UltiMaker-Cura.exe 33600 FileSystemControl \My_Server_UNC\Path\ NOT REPARSE POINT Control: FSCTL_GET_REPARSE_POINT
17:22:59.6 UltiMaker-Cura.exe 33600 FileSystemControl \My_Server_UNC\Path\ NOT REPARSE POINT Control: FSCTL_GET_REPARSE_POINT
17:23:04.6 UltiMaker-Cura.exe 33600 FileSystemControl \My_Server_UNC\Path\ NOT REPARSE POINT Control: FSCTL_GET_REPARSE_POINT

(the last 4 are the mapped drive that isn't available when elevated, the same as QueryDeviceInformationVolume in the below table; I also killed the process before stopping the capture, so there's exiting showing in the not working)

For the HKLM\System\CurrentControlSet\Services\WinSock2\Parameters, it retries each time with Desired Access: Read and is successful.

For the HKLM\System\CurrentControlSet\Services\EventLog\Application\NVIDIA OpenGL Driver, it does not retry.

The log ProcMan output for unsuccessful run started at 17:22:44 and finished at 17:23:10 (26 seconds) - It generated 254,645 entries The log ProcMan output for the successful run started at 17:19:49 and finished at 17:20:07 (19 seconds) - It generated 254,100 entries

The counts of each operation is relatively similar:

NOT WORKING Count   WORKING Count Not Working - Working
CreateFile 55376   CreateFile 55468 -92
CloseFile 32767   CloseFile 32898 -131
QueryAllInformationFile 28138   QueryAllInformationFile 28703 -565
QueryInformationVolume 28138   QueryInformationVolume 28703 -565
RegOpenKey 22979   RegOpenKey 22565 414
RegQueryKey 19014   RegQueryKey 18473 541
RegCloseKey 16829   RegCloseKey 16524 305
RegQueryValue 14741   RegQueryValue 14514 227
ReadFile 12994   ReadFile 13023 -29
QueryNameInformationFile 6131   QueryNameInformationFile 6133 -2
QueryDirectory 5191   QueryDirectory 5191 0
QueryNormalizedNameInformationFile 2999   QueryNormalizedNameInformationFile 3000 -1
QueryRemoteProtocolInformation 2055   QueryRemoteProtocolInformation 2055 0
QueryNetworkOpenInformationFile 1201   QueryNetworkOpenInformationFile 1135 66
CreateFileMapping 1084   CreateFileMapping 1062 22
RegEnumKey 957   RegEnumKey 826 131
QueryStandardInformationFile 811   QueryStandardInformationFile 801 10
QueryBasicInformationFile 649   QueryBasicInformationFile 634 15
WriteFile 606   WriteFile 616 -10
Load Image 328   Load Image 321 7
TCP Receive 324   TCP Receive 241 83
RegSetInfoKey 288   RegSetInfoKey 283 5
FileSystemControl 247   FileSystemControl 243 4
TCP TCPCopy 162   TCP TCPCopy 134 28
TCP Send 113   TCP Send 95 18
Thread Create 104   Thread Create 104 0
RegEnumValue 102   RegEnumValue 102 0
Thread Exit 85   Thread Exit 6 79
RegCreateKey 48   RegCreateKey 41 7
UDP Receive 40   UDP Receive 68 -28
QueryAttributeInformationVolume 36   QueryAttributeInformationVolume 36 0
UDP Send 20   UDP Send 16 4
QueryAttributeTagFile 18   QueryAttributeTagFile 20 -2
SetDispositionInformationEx 10   SetDispositionInformationEx 10 0
LockFile 8   LockFile 8 0
TCP Connect 7   TCP Connect 7 0
QuerySecurityFile 7   QuerySecurityFile 4 3
UnlockFileSingle 6   UnlockFileSingle 6 0
QueryEAFile 4   QueryEAFile 4 0
Process Create 4   Process Create 3 1
SetDispositionInformationFile 4   SetDispositionInformationFile 4 0
QueryDeviceInformationVolume 4       4
TCP Accept 3   TCP Accept 3 0
RegSetValue 3   RegSetValue 4 -1
SetRenameInformationFile 2   SetRenameInformationFile 4 -2
Process Start 2   Process Start 2 0
FlushBuffersFile 2   FlushBuffersFile 4 -2
RegQueryKeySecurity 1   RegQueryKeySecurity 1 0
NotifyChangeDirectory 1   NotifyChangeDirectory 1 0
Process Exit 1       1
Grand Total 254644   Grand Total 254099 545

I don't think there's a significant difference.

Both access the following reg keys the number of times shown in the Count column (note that some are duplicates, just in Title Case or CAPITALS). There are other things in between, but why the same reg keys around 4k / 2k times?!:

Time of Day Process Name PID Operation Path Result Detail Count
17:22:49.7 UltiMaker-Cura.exe 33600 RegOpenKey HKLM\Software\Microsoft\Windows\CurrentVersion\Explorer\Desktop\NameSpace_36354489 SUCCESS Desired Access: Query Value 4046
17:22:49.7 UltiMaker-Cura.exe 33600 RegCloseKey HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Desktop\NameSpace_36354489 SUCCESS   4046
17:22:49.7 UltiMaker-Cura.exe 33600 RegOpenKey HKLM\Software\Microsoft\Windows\CurrentVersion\Explorer\Desktop\NameSpace SUCCESS Desired Access: Query Value 4314
17:22:49.7 UltiMaker-Cura.exe 33600 RegQueryValue HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Desktop\NameSpace\ValidateRegItems NAME NOT FOUND Length: 16 4046
17:22:49.7 UltiMaker-Cura.exe 33600 RegCloseKey HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Desktop\NameSpace SUCCESS   4314

They both try to access the following three reg keys 759 times (253 time each):

HKLM\System\CurrentControlSet\Control\DeviceClasses{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}##?#STORAGE#Volume#{9195986c-629c-11ed-9696-806e6f6e6963}#0000000007500000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}#\Properties{4d1ebee8-0803-4774-9842-b77db50265e9}\0004

HKLM\System\CurrentControlSet\Control\DeviceClasses{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}##?#STORAGE#Volume#{9195986c-629c-11ed-9696-806e6f6e6963}#0000000007500000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}#\Properties{4d1ebee8-0803-4774-9842-b77db50265e9}\0004

HKLM\System\CurrentControlSet\Control\DeviceClasses{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}##?#STORAGE#Volume#{9195986c-629c-11ed-9696-806e6f6e6963}#0000000007500000#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}#\Properties{4d1ebee8-0803-4774-9842-b77db50265e9}\0004(Default)

Could the ACCESS DENIED for the NVIDIA OpenGL Driver have any bearing on this? - And yes, I have an NVIDIA GPU.

I can't run the Extensive Support Logging extension, because I never get to a point where I can use the menu bar.

AubsUK commented 1 year ago

Summary of my last post!!

MariMakes commented 1 year ago

Hey All,

Quick update from our side. We've released a nightly build to check a potential fix for Windows users who have trouble with multiple monitors. But we've also received a report that it speeds up performance.

Could you check and report if you are seeing a speed increase? You can find the download here: https://github.com/Ultimaker/Cura/discussions/15098

daBigR-- commented 1 year ago

I hadn't reported any issues before but I was having extremely low response times when moving objects and similar operations where Cura would consume most of my CPU and memory (Win 11, NVIDIA graphics card) . I've been using the nightly build for a few hours now and the improvement is very noticeable, Cura is as responsive as it always had been before 5.2. Thanks Mariska.