Application Startup Broken (Doesnt Start) #8623
Labels
Type: Bug
The code does not produce the intended behavior.
Comments
|
Here is a longer log snippet from my desktop, the delay is still there but closer to 5 minutes which may reflect the compute differential compared to the OP log provided from my laptop. |
|
Do you perhaps have a drive mapped to the letter X that is not currently connected? If so, could you try mapping that drive to a different driveletter? |
|
@fieldOfView On my Desktop I have a network drive mapped to "S:" and nothing on my laptop, neither has any mapping or drives assigned to "X:" |
|
We can rule out the version upgrade and the loading of the metadata here. Both are timed almost completely. These are the things that are done in between, in the start-up sequence:
One thing that could feasibly take a long time is adding the system tray icon, since that is kind of dependent on the operating system which is at liberty to block such things. This is also a visible part of the process. Perhaps you can start Cura to see if the system tray icon is there? If it is, the slow part must be somewhere after that in the process. If there is no system tray icon, the slow part was before that or the system tray icon itself. Another thing that would help is to have more logging in our code regarding this. There are quite a few steps here that don't get a log entry. They should though... |
|
@Ghostkeeper I tried to re-run to check tray icon, alas it is now loading correctly. I guess this can technically be closed now, but, having Cura magically break and become unusable for a week, then magically fix itself, is problematic at best. I would suggest if this can somehow get in someone's backlog, to add the additional logging you indicated above, otherwise it will be near impossible to troubleshoot this if it crops up again. Thanks for the support |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Application version
4.7.0 & 4.7.1 (at least)
Platform
Windows 10 2004 and Insider 10.0.20241.1005
Printer
(Custom) Ender3V2
Reproduction steps
(Multiple Independent machines/installations all affected)
2.1) Click on splash screen, windows reports Cura.exe not responding, begins windows crash flow.
2.2) Chask task manager for cura.exe process/ram/network/file system images, no indication of issue all values very low for exe and system
2.3) Check log file, no errors in the tail to indicate the issue, few warnings about inability to load unnamed plugin.
2.4) Force close process
2.5 repeat several times, no change in behavior across reboots, task kills, upgrade to 4.7.1, etc
As I had not changed anything my expectation was that some remote/network integration is failing, or a settings config was corrupted and Cura hangs unable to log and recover from such failure.
I tried 4 days later hoping any remote depedency that had broken might be repaired but same result.
And then I walked away and came back 30 minutes later to find Cura loaded(!!!) which seems to indicate my profiles/settings are still valid.
Trying to repro I found that Cura hangs for 20 mintutes between the 2 below log lines, with no indication why, but all loading before and after the hang proceeds as normal.
**This happens on multiple machines with vastly different hardware installed that all worked just fine this time last week but now all suffer this issue with no changes on my part.
Screenshot(s)
N/A
Actual results
App startup hangs for 20 minutes
Expected results
No delay should occur
Project file
N/A
Log file
(TLDR)
2020-10-26 15:39:25,034 - DEBUG - [MainThread] UM.PluginRegistry.loadPlugins [373]: Loading all plugins took 2.7668869495391846 seconds
2020-10-26 15:39:25,049 - INFO - [MainThread] UM.VersionUpgradeManager.upgrade [163]: Looking for old configuration files to upgrade.
2020-10-26 15:39:25,400 - INFO - [MainThread] UM.VersionUpgradeManager.upgrade [175]: Checking and performing updates took 0.35339903831481934
2020-10-26 15:58:18,186 - DEBUG - [MainThread] UM.Settings.ContainerRegistry.loadAllMetadata [361]: Loading metadata into container registry took 1.0665972232818604 seconds
2020-10-26 15:58:18,203 - DEBUG - [MainThread] cura.Scene.CuraSceneController.setActiveBuildPlate [142]: Select build plate: 0
20 minutes bewtween log lines with no error or warning
(FULL)
will provided if needed
Additional information
repro'd on fully loaded core7/intel grfx Lenovo X1 Yoga and custom Desktop AMD Threadripper / Radeon 7 grfx fast and lots of ram/pcie ssd.
The text was updated successfully, but these errors were encountered: