Closed strongly-typed closed 2 years ago
Hi @strongly-typed,
Thanks for your bug report. Unfortunately, I cannot reproduce the issue. Judging from the logfile this seems like a hard crash, so it's a bit hard to find the root cause without some further information. Could you please let us know about the following:
Hi @strongly-typed,
Thanks for your bug report. Unfortunately, I cannot reproduce the issue. Judging from the logfile this seems like a hard crash, so it's a bit hard to find the root cause without some further information. Could you please let us know about the following:
Thanks for looking into this issue.
- Is there no actual Cura crash report? I see only the crash from what I assume must be the Console.app.
Report is from the dialog "Ultimaker Cura quit unexpectedly" from Apple.
I cannot see a crash log:
➜ 4.12 ll
total 80
drwxr-xr-x 4 sascha staff 128B Nov 2 14:41 cache
-rw------- 1 sascha staff 918B Nov 2 14:42 cura.cfg
-rw-r--r-- 1 sascha staff 28K Nov 2 14:42 cura.log
drwxr-xr-x 2 sascha staff 64B Nov 2 14:41 definition_changes
drwxr-xr-x 2 sascha staff 64B Nov 2 14:41 definitions
drwxr-xr-x 2 sascha staff 64B Nov 2 14:41 extruders
drwxr-xr-x 2 sascha staff 64B Nov 2 14:41 intent
drwxr-xr-x 2 sascha staff 64B Nov 2 14:41 machine_instances
drwxr-xr-x 2 sascha staff 64B Nov 2 14:41 materials
-rw-r--r-- 1 sascha staff 105B Nov 2 14:41 packages.json
drwxr-xr-x 2 sascha staff 64B Nov 2 14:41 plugins
-rw-r--r-- 1 sascha staff 51B Nov 2 14:41 plugins.json
drwxr-xr-x 2 sascha staff 64B Nov 2 14:41 quality
drwxr-xr-x 2 sascha staff 64B Nov 2 14:41 quality_changes
drwxr-xr-x 2 sascha staff 64B Nov 2 14:41 scripts
drwxr-xr-x 2 sascha staff 64B Nov 2 14:41 setting_visibility
drwxr-xr-x 2 sascha staff 64B Nov 2 14:41 themes
drwxr-xr-x 2 sascha staff 64B Nov 2 14:41 user
drwxr-xr-x 2 sascha staff 64B Nov 2 14:41 variants
- Are you logged in to Cura?
No, I am not. I did the tests with the machine disconnected from the Internet (WiFi switched off)
- Are both printers part of the same network or is perhaps your S5 connected via cloud?
No, totally offline. I was following this click through for testing:
Welcome -> Get started -> Agree -> More information -> I don't -> OK -> Next -> Skip -> Add a non-networked printer -> Ultimaker S5 -> Next
Then displays the intro dialog and crashes after 2 to 3 seconds.
- Did Cura suddenly start crashing when using 4.11 or was it always like that?
4.10 worked fine for a while. Then started crashing when switching between printers. That's why I tried upgrading to 4.11 and then 4.12 beta. 4.10 does not work anymore.
- Does Cura 4.10 have the same issues? Yes, also 4.8, 4.0 and even 2.7 (!)
My guess is that this is somehow related to the latest update of MacOS 10.15.7 (19H1519) and/or the graphics drivers?!
The logs look correct to me. Cura's log is there. And so is the crash log from MacOS about Cura crashing.
My guess is that this is somehow related to the latest update of MacOS 10.15.7 (19H1519) and/or the graphics drivers?!
I think you're right. What I see in the crash log is Cura processing Qt's event loop. That event loop triggers a re-render in Qt. Qt calls upon the Intel drivers to render something with a texture, and the drivers crash on storing that texture on the GPU. From your description it appears that it might be the texture on the S5 build plate causing this. But the GPU should just be able to load in a texture. I'm not sure what we can really do about this if it can't.
I installed Cura 4.12.0 release using brew. Unfortunately, the issue persists.
2021-11-14 00:48:43,832 - DEBUG - [MainThread] UM.View.GL.OpenGL.__init__ [112]: Initialized OpenGL subsystems.
2021-11-14 00:48:43,836 - DEBUG - [MainThread] UM.View.GL.OpenGL.__init__ [113]: OpenGL Version: 4.1 INTEL-14.7.20
2021-11-14 00:48:43,841 - DEBUG - [MainThread] UM.View.GL.OpenGL.__init__ [114]: OpenGL Vendor: Intel Inc.
2021-11-14 00:48:43,845 - DEBUG - [MainThread] UM.View.GL.OpenGL.__init__ [115]: OpenGL Renderer: Intel HD Graphics 4000 OpenGL Engine
2021-11-14 00:48:43,849 - DEBUG - [MainThread] UM.View.GL.OpenGL.__init__ [116]: GLSL Version: 4.10.0
Is there a way to remove the texture locally?
The crash seems to be related to the Security Update 2021-007 macOS Catalina which breaks the Intel HD Graphics 4000 OpenGL Driver
https://communities.apple.com/de/thread/253320172?page=1
https://discussions.apple.com/thread/253309962?answerId=256269441022&page=1
Interestingly, Safari works again when enabling WebGL via Metal
:
https://discussions.apple.com/thread/253309962?answerId=256269441022&page=1
Is there a way that Cura will be using Metal as well?
Is there a way that Cura will be using Metal as well?
Not any time soon. It would mean we would have to support multiple graphical backends. This would double the maintenance load for this part of the code. If only OSx would have decided to support a graphical system that is supported by other operating systems, things would have been so much easier.
Is there a way to remove the texture locally?
Not easily on MacOS. The texture and reference to that texture are packed in the application archive, and editing that archive will cause the signature check to fail that MacOS does. You could make a new definition (or copy the definition you're using) and remove the platform_texture
metadata entry. Custom definitions are loaded from $HOME/Library/Application Support/cura/<Cura version>/definitions
.
That is a workaround, but quite a technical/difficult one for most people.
Thanks for your replies and effort you put into this.
Yesterday, Apple rolled out Security Update 2021-008 (Catalina) which seems to have fixed the bug.
Still running an Early 2013 MBP in full production ...
Application Version
4.11 and 4.12 BETA
Platform
macOS Catalina 10.15.7 (19H1519)
Printer
Ultimaker S5
Reproduction steps
I had Cura 4.11 and two printers installed, Ultimaker S5 and Ender 3. Cura started crashing when switching from one printer to other.
I then upgraded to 4.12 BETA. Problem persisted.
Delete
~/Library/Application Support/cura
entirely and started from scratch setting up Cura.Cura now crashes in the Add a Printer dialog when selecting
Next
after selecting the found printer.Actual results
Cura just crashes
cura.log from tonight
Expected results
Printer should be added and switching between two printers should be possible.
Checklist of files to include
Additional information & file uploads
Independent of project. Also crashed with no file loaded.
Adding an Ender 3 works flawlessly. Ultimaker S5 and S3 crash.