(Bug): Natron crashes on macOS Monterey with Qt4 #712
Comments
devernay
added
difficulty:hard
|
I can't go beyond BigSur, so can't test. Looks like Qt4 has issues with the menu bar. This https://bugreports.qt.io/browse/QTBUG-25399 looks related. |
|
I'm having the same issue. It doesn't even let me open up a project. It just crashes within 5 seconds of opening. both 2.4.0 and 2.4.1 had the same issue iMac (Retina 5K, 27-inch, 2020) |
|
The good news is that the (pre-alpha) Qt5 build seems to fix this, |
|
Anytime I open Natron at all it crashes on Monterey |
|
same backtrace as https://bugreports.qt.io/browse/QTBUG-25399 |
|
This seems to be an old issue, which resurfaced in Monterey for some reason: I will try to add the check for NULL in QAction::isEnabled() to fix the symptom. |
yes, i can second that - i'm on macOs 12.1 |
|
Ok so it looks like a deep Qt4 bug: Qt is making some assumption about how events are handled by macOS, and this assumption was violated in Monterey. I was secretly hoping it was a Monterey bug and it would be fixed in 12.1, but it's not the case. Closing any window, including the "Loding project" splash screen, causes a crash. 2.4.2 will disable this splash screen on Monterey, which should allow working on Monterey, although opening more than one project and then closing one will crash. |
|
Monterey binary available from https://github.com/NatronGitHub/Natron/releases/tag/v2.4.2 |
devernay
changed the title
|
Been on a long suggested vacation. Will back at work on Monday to test it again. |
|
I had downloaded the 2.4.2 link for MacOS12 this is the error log report crash Translated Report (Full Report Below)Process: Natron [3345] Date/Time: 2022-01-21 10:28:25.4526 -0500 Time Awake Since Boot: 1000 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 VM Region Info: 0x676c6f6a is not in any region. Bytes before following region: 2791555222 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread Thread 1: Thread 2: Thread 3:: com.apple.CFSocket.private Thread 4:: com.apple.NSEventThread Thread 5: Thread 6: Thread 7: Thread 0 crashed with X86 Thread State (64-bit): Logical CPU: 1 Thread 0 instruction stream: Binary Images: External Modification Summary: VM Region Summary: REGION TYPE SIZE COUNT (non-coalesced) Full Report{"app_name":"Natron","timestamp":"2022-01-21 10:28:25.00 -0500","app_version":"2.4.2","slice_uuid":"35a99693-d2d2-37d6-8327-b376832330d3","build_version":"2.4.2","platform":1,"bundleID":"fr.inria.Natron","share_with_app_devs":1,"is_first_party":0,"bug_type":"309","os_version":"macOS 12.1 (21C52)","incident_id":"BE65D49D-59A1-4465-93AD-5D7C77804192","name":"Natron"} ], ] Model: iMac19,1, BootROM 1715.60.4.0.0, 6 processors, 6-Core Intel Core i5, 3.7 GHz, 64 GB, SMC 2.46f12 |
|
I’ll post my crash report merely to acknowledge the bug is still there. Translated Report (Full Report Below)Process: Natron [1558] Date/Time: 2022-03-19 10:53:57.4557 +0300 Time Awake Since Boot: 1200 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 VM Region Info: 0x676c6f6a is not in any region. Bytes before following region: 2692747414 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread Thread 1: Thread 2: Thread 3: Thread 4: Thread 5:: Global Thread (Pooled) (0x600001682968) Thread 6:: com.apple.CFSocket.private Thread 7:: com.apple.NSEventThread Thread 0 crashed with X86 Thread State (64-bit): Logical CPU: 2 Thread 0 instruction stream: Binary Images: External Modification Summary: VM Region Summary: REGION TYPE SIZE COUNT (non-coalesced) Full Report{"app_name":"Natron","timestamp":"2022-03-19 10:53:57.00 +0300","app_version":"2.4.3","slice_uuid":"e01d4315-d609-36c9-9310-d25a8f7533fc","build_version":"2.4.3","platform":1,"bundleID":"fr.inria.Natron","share_with_app_devs":0,"is_first_party":0,"bug_type":"309","os_version":"macOS 12.2.1 (21D62)","incident_id":"6EE17624-7E2E-47B7-96B7-53B4A1D446EC","name":"Natron"} ], ] Model: MacBookPro16,1, BootROM 1715.81.2.0.0 (iBridge: 19.16.10744.0.0,0), 8 processors, 8-Core Intel Core i9, 2.3 GHz, 16 GB, SMC |
Issues with macOS 12 will not get fixed until we move to Qt5 (Natron 2.6), as this is a issue with Qt4 vs. macOS 12.
Why? Natron works fine on older versions of macOS, expecially pre 10.15. There was some issues with 10.15 and 11, but they are fixed I believe (I have not tested 10.15, but 11 seems to work fine). |
|
i'm on macOs12.3 and Natron 2.4.2 runs totally fine do you use the macOs12 releases? |
i thought i did. i redownloaded and reinstalled it after i saw your message and it indeed does work. i stand corrected. |
|
Not sure whether this bug is still relevant, but at least the issue is still marked as "Open". We had the exact same problem with a different Qt 4 project, and we found that the bug can at least be worked around by simply not using the native macOS menu bar. Using the native macOS menu bar can be disabled by inserting the following code before creating the menu bar:
I've also posted some more details about this issue here. |
|
Solution: use a Qt5 build (natron 2.6) |
Problem
When loading any project from the menu (or cmd-O shortcut) on macOS Monterey 12.0.1-12.1, Natron 2.1.9-2.5.0 crashes.
Natron 2.0.5 doesn't crash.
New: Natron 2.4.2 seems to still crash (#731), although the "loading project" splash screen was disabled - maybe we also need to disable the startup splash screen? Waiting for feedback from @blackearth2014 to know if the first splash screen is displayed or if the crash happens before.
Sometimes, loading from the finder (dbl-click on project file) works, sometimes it still crashes, either immediately or a bit later.
Here are sample project files to try (these are reproductibility projects for #708):
Archive.zip
This is a major issue, that prevents using Natron properly on Monterey.
backtrace 1 (with Natron 2.4.1):
backtrace 2 (with Natron 2.4.1):
The text was updated successfully, but these errors were encountered: