jatkinson10
commented
3 years ago I'm also experiencing the same issues. 4.8 worked flawlessly, however, 4.9.x has been problematic since I updated.
Open NoTrace-Kai opened 3 years ago
jatkinson10
commented
3 years ago I'm also experiencing the same issues. 4.8 worked flawlessly, however, 4.9.x has been problematic since I updated.
mbourque
commented
3 years ago I also experience this quite often
fvrmr
commented
3 years ago Hi @NoTrace-Kai thank you for your bug report. Do you have a Macbook with M1? I will discuss this with the team. Keep you posted!
fvrmr
commented
3 years ago @NoTrace-Kai I have discussed it with the team and if you have a M1 then we can't really help you right now since we don't support M1. There are incompatibilities between the OpenGL libraries used and the latest firmware used by macbooks.
If you don't have a M1 we need to investigate this further.
NoTrace-Kai
commented
3 years ago Hi.
Thanks a lot for your answer. My MacBook Air is a 2020 with Intel i7 CPU, 16GB RAM and 512GB SSD.
Greetings Kai
fvrmr
commented
3 years ago Thank you, do you maybe have a second monitor?
NoTrace-Kai
commented
3 years ago No. Only the one from the MacBook Air.
Ghostkeeper
commented
3 years ago By the looks of that stack trace, Qt crashed while it was executing some of the Javascript code in the QML files. Qt should never crash, so it is a bug in their side. In the update to Cura 4.9 we updated the version of Qt to a newer version, so this might be a bug that arose in one of the newer versions.
Another possibility is simply that your computer ran out of memory, since the instruction it apparently crashes on is a Malloc (allocating memory). Cura typically uses like 200-500MB memory though, so unless you had some real heavy stuff running in the background that shouldn't have been a problem for your computer.
Assuming the first possibility there, it's possible that there is a workaround for us. Maybe we should avoid using a certain function in Javascript, or a certain type of syntax. However it's pretty much impossible for us to know what Javascript is causing this issue. We haven't been able to reproduce this issue in any of our testing computers. If we have a reproduction, we could try figuring this out with a debugger looking into the memory of Qt to determine which QML file is causing the issue, and perhaps where in that file it's going wrong. But until then, there is little we can hope to achieve here.
Z122-JPL
commented
2 years ago @NoTrace-Kai , I wonder if this problem could be solved by this solution : https://github.com/Ultimaker/Cura/issues/10789#issuecomment-968054449
@jatkinson10 , @mbourque , @Ghostkeeper Here is the official fixing solution, just published few hours ago : https://support.ultimaker.com/hc/en-us/articles/4410029795474
Application Version
4.9.0 and 4.9.1
Platform
Mac OS Big Sur
Printer
Ender 3 V2
Reproduction steps
Just when i want to open the Cura App
Actual results
The Crash-Log is shown
Expected results
Also after installing Cura 4.9.0 the error is there ...
Checklist of files to include
Additional information & file uploads