Magic 2.5 Crashes on Scene Switching (Segmentation Fault)
Posted: Mon Aug 17, 2026 1:25 pm
Magic 2.5 Crashes on Scene Switching (Segmentation Fault)
Magic 2.5 crashes with a segmentation fault when switching between scenes in module canvases. The crash occurs consistently within minutes of launching the app during scene transitions. Both crashes are identical in structure but corrupt different system frameworks, suggesting a memory safety issue in the rendering pipeline. It started today, didn't have any issues with projects before, now happens with every project and tabs.
Environment
Magic version: 2.5
OS: macOS 26.5.2 (25F84)
Mac model: Mac16,8 (Apple Silicon, running via Rosetta translation)
System Integrity Protection: Enabled
Crash Details
Exception: EXC_BAD_ACCESS (SIGSEGV) — Segmentation fault: 11
Crash 1 (15:03:53):
Corrupted framework: CoreAutoLayout.framework
Invalid memory address: 0x011dfff85327be71
Session duration: ~45 minutes before crash
Crash 2 (15:08:33):
Corrupted framework: Metal.framework
Invalid memory address: 0x011dfff85328d251
Session duration: ~5 minutes before crash
Note: More threads active (52 total, including video decode threads)
Stack Trace Pattern
Both crashes follow the same call path:
Magic internal methods → AppKit view drawing → CoreAnimation rendering → System framework corruption
Triggered by Thread 0 (Juce Message Thread) during display rendering.
Reproducibility
Occurs reliably when switching scenes
Happens faster on projects with active video processing
May be related to concurrent rendering during scene transitions
I can provide the crash logs if needed
Questions
Is this a known issue in 2.5? This happened as of today, no problems before.
Any workarounds until a fix is available?
Magic 2.5 crashes with a segmentation fault when switching between scenes in module canvases. The crash occurs consistently within minutes of launching the app during scene transitions. Both crashes are identical in structure but corrupt different system frameworks, suggesting a memory safety issue in the rendering pipeline. It started today, didn't have any issues with projects before, now happens with every project and tabs.
Environment
Magic version: 2.5
OS: macOS 26.5.2 (25F84)
Mac model: Mac16,8 (Apple Silicon, running via Rosetta translation)
System Integrity Protection: Enabled
Crash Details
Exception: EXC_BAD_ACCESS (SIGSEGV) — Segmentation fault: 11
Crash 1 (15:03:53):
Corrupted framework: CoreAutoLayout.framework
Invalid memory address: 0x011dfff85327be71
Session duration: ~45 minutes before crash
Crash 2 (15:08:33):
Corrupted framework: Metal.framework
Invalid memory address: 0x011dfff85328d251
Session duration: ~5 minutes before crash
Note: More threads active (52 total, including video decode threads)
Stack Trace Pattern
Both crashes follow the same call path:
Magic internal methods → AppKit view drawing → CoreAnimation rendering → System framework corruption
Triggered by Thread 0 (Juce Message Thread) during display rendering.
Reproducibility
Occurs reliably when switching scenes
Happens faster on projects with active video processing
May be related to concurrent rendering during scene transitions
I can provide the crash logs if needed
Questions
Is this a known issue in 2.5? This happened as of today, no problems before.
Any workarounds until a fix is available?