Blank screen and freeze on start-up #8892
Labels
Status: Needs Info
Needs more information before action can be taken.
Status: Stale ⌛
This issue is over a year old. It might be obsolete or just needs a fresh set of eyes
Type: Bug
The code does not produce the intended behavior.
Comments
|
Short answer: Please reinstall graphics card drivers. Longer explanation: As you can see, the OpenGL version is 4.1.0, while the GLSL version is 400. This should never happen. OpenGL version 4.1.0 is locked to GLSL 410. I've seen this in the past, and the re-installation of graphics cards drivers fixed the problem for at least one reporter (maybe more). |
|
Crash on startup : White screen #8904 |
|
@Devtech223 I hadn't seen that one, thanks for pointing it out! Are your 'reproduction steps' the same as @MooM00 s? I'm going to close the newer issue #8904 as a duplicate (keeping this one open so we can track it), but I think it's useful to at least put the workaround found in the other issue here so people don't have to play 'follow the link':
Reproduction steps seem to have something to do with having 2 monitors. I use 2 monitors as well, but the primary one is on the right at the moment. |
|
With multiple monitors, try temporarily disabling one. If Cura starts with only a single display, then go to the General preferences in Cura and deselect the option to "Restore window position on start". Then you can reenable the second display. |
This comment has been minimized.
This comment has been minimized.
Well, you are great at motivational speaking, so you have that going for you.
Feel free to participate in issues, but please try to chime in where it is relevant. Yours is a very different problem than what is being discussed in this issue. See #8472 |
|
Also crashes on Intel HD 2500 with OpenGL 3.1. Some additional features are supported from newer versions too: Please keep compatibility with old HW, there is no point buying new PC only for slicing. (I wouldn't call displaying a 3D model as cutting edge application), let's think green. Also it would be time to do CPU/memory profiling, it's getting slower and slower even on my 4core desktop, and eating 500MB RAM, with >20-30sec startup. |
|
We know what things are supported by various OpenGL versions, there no need to tell us again. We also regularly profile Cura. But as others have already posted before; Without adding extra information about your system, saying that the issue occurs with you is simply not helping. |
|
I just included what OpenGL features are supported by my older Intel card, so simulation could be fixed for it. Please find my 4.8 crash logs attached: |
|
If OpenGL 4.1 is not available it should fall back to OpenGL 2.0, which should be supported through backwards compatibility by your chip. Indeed you won't have the simulation view available but at least it should run and be able to see layer view data, albeit more flat and less fully-featured. The crash dialogue indicates that there is a segfault ( |
|
Thanks for the investigation, would OpenGL 2.0 generate worse gcode? Looks like the Windows Intel driver is buggy, I will try to upgrade it. Until then I have to stick with Cura 4.7. |
|
OpenGL does not in any way affect the gcode that is created. |
The workaround worked for me. This issue is still present in 4.8.0. |
|
What finally worked for me on 4.8 was to click on the Learn More of the last intro slide (before the crash) and change the setting to not share info with Cura. Changing the setting and accepting the change allowed the installation to completed. Changing to a single monitor/powering off/disconnecting, etc. did not make a difference for me as it did for some. Good luck! |
|
It's weird that for some people changing that preference apparently helps get them through the start-up wizard, especially since the anonymous slice information is only sent when saving the g-code or sending it to the printer. The preference is not used in the start-up wizard at all. You can search the source code here for usages of the |
|
I was having this same issue intermittently on macOS on my 2017 15-inch Macbook Pro, also seems related to Graphics Drivers. None of the above workarounds fixed it for me but I seem to have figured something out. For context, my MBP has Intel HD 630 graphics and a Radeon Pro 560 4 GB.
Given that it worked intermittently I took a close reading of the logs and found out that when it didn't work it used my Intel graphics: and when it did work it used my Radeon card: What's interesting is now after this debugging session constantly starting/stopping Cura with the different GPUs I am no longer able to repro the issue at all, it starts fine on both. I didn't go messing around in any settings so I'm not sure why that would be. One can force their mac to always use discrete graphics (if available) by unchecking Automatic Graphics Switching in the power settings. For more granular control there's also gfxCardStatus which lets you force integrated or discrete, and shows why it picked one or the other. I'm happy to provide full logs or anything else needed for more clues. Hope this helps! |
This worked for me in 4.9.0. Thanks @fieldOfView! |
Thank you, I got this issue after upgrading from macOS 11.1 to 11.3.1! |
I can confirm it was due to two monitors. |
|
We've made some changes to 4.10 that might affect this issue. A number of people have reported that issues with multiple monitors have been resolved in 4.10 |
|
Had the same issue. I have an i7 late 2014 Mac mini with Dual Thunderbolt Displays along with an EGPU attached. Somewhere in some update using the EGPU to render vs the internal gpu causes the white screen. Disabling "prefer EGPU" restored Cura back to normal. Cura upgrades did not resolve the issue. I used to render using my egpu previously with no issues. |
|
Hey, I encounter Cura crashing on me too, tried to disable screens and launch it but didn't help. Deleted the cura.cfg and that didn't help either. Here's the log: Happens with 5.0 and 4.13 FIXED IT BY STOPPING ASUS GPU TWEAK SOFTWARE THAT CAME WITH MY TUF 3060TI! |
Hi, I just created my github account to thank and confirm this solution, I've been having the same issue (Cura closing after loading every time) with a previous and the latest Cura versions, closed GPU Tweak II and Cura is running fine again. Then it occurred to me that the OSD overlay might be trying to interact with the Cura window, and indeed, I can confirm (at least in my case) that the problem is the GPU Tweak OSD overlay, I have Cura running with GPU Tweak but the OSD overlay off. I hope this helps. |
This was referenced Oct 27, 2022
2 tasks
|
Is this still an issue in current Cura versions (5.8.0 and up)? Can this be closed? |
|
IMO, an update solves it, so it could be closed.
Le mer. 20 nov. 2024, 03:43, GregValiant ***@***.***> a
écrit :
… Is this still an issue in current Cura versions (5.8.0 and up)? Can this
be closed?
—
Reply to this email directly, view it on GitHub
<#8892 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMUPSVUZPBPY5WL3GJIBJD2BPZLTAVCNFSM6AAAAABSDQR74WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOBXGIZDKNZUGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Thanks. I'm cleaning house here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Application version
4.8
Platform
Windows 10 Nvida 2060Super GPU
Printer
Ender 3V2
Reproduction steps
won't load gives me only a blank white screen and stops responding in task manager
Screenshot(s)
Actual results
Expected results
Project file
(For slicing bugs, provide a project which clearly shows the bug, by going to File->Save Project. For big files you may need to use WeTransfer or similar file sharing sites. G-code files are not project files!)
Log file
Additional information
(Extra information relevant to the issue.)
The text was updated successfully, but these errors were encountered: