Logic Pro X crashes after minutes after I…

Final Cut Pro crashing for the past 2 weeks Hi, I use Final Cut Pro 10.6.7 with MacOS Ventura 13.4.1 (c) every day on my Mac Mini and my MacBook. For the past 2 weeks, the program crashes every 15 minutes roughly on both machines and on various projects. I thought it was maybe a bug in one of my edits but since it's happening on both machines and different projects, I think it's a different issue. Has anyone else been experiencing this? In my years using FCP since 2011, it's never been like this. Here is the beginning of the crash report if that's any help. Process: Final Cut Pro [17834] Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro Identifier: com.apple.FinalCut Version: 10.6.7 (408080) Build Info: ProEditor-40800080016000000~4 (20A104) App Item ID: 424389933 App External ID: 858081843 Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 502 Date/Time: 2023-07-28 17:14:45.9389 -0400 OS Version: macOS 13.4.1 (22F770820d) Report Version: 12 Anonymous UUID: E81A29D0-98BC-6A7F-F4F7-E320328CEDB6 Sleep/Wake UUID: 1BD0AE1E-DCCF-4474-B22E-E63C6B1D5284 Time Awake Since Boot: 22000 seconds Time Since Wake: 7257 seconds System Integrity Protection: enabled Crashed Thread: 82 Dispatch queue: com.apple.helium.rq.gpu-ru1.vs0.gcd Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 Exception Codes: 0x0000000000000001, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler [17834] VM Region Info: 0 is not in any region. Bytes before following region: 4368809984 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START ---> __TEXT 10466c000-104748000 [ 880K] r-x/r-x SM=COW ...Final Cut Pro

3945 14

Logic Pro 11.1.2 crashes immediately on launch It was working perfectly fine a couple days ago. When I tried to open Logic to work on some stuff this morning, it refused to launch and gave me a Problem Report. A screen recording of the problem is attached below, and I can share the full problem report if it would be helpful to anyone, but I put it into ChatGPT and this was its response: The crash report indicates that Logic Pro crashed in Thread 8, which was responsible for a task related to CoreML (Apple’s Core Machine Learning framework). Here’s a breakdown of what likely went wrong: 1. Faulting Area: • The crash occurred in com.apple.coreml.MLE5ProgramLibrary.lazyInitQueue, suggesting that an issue arose while initializing a CoreML-related component. This may relate to machine learning or AI-based plugins or features within Logic Pro. 2. Exception Details: • Type: EXC_CRASH (SIGABRT) • Reason: Abort trap: 6. This generally means the application aborted itself, often due to an unhandled exception or internal assertion failure. 3. Library Involvement: • MPSGraphExecutable and E5RT::Ops indicate involvement of MetalPerformanceShadersGraph and Espresso, which handle machine learning operations. The crash seems to occur while setting up a machine learning model or executing a precompiled operation. 4. Potential Causes: • A plugin, feature, or setting that uses CoreML (e.g., AI-driven tools like Smart Tempo or adaptive processing). • Corrupted machine learning models or libraries. • Incompatibility between the current version of Logic Pro and the installed macOS version or other software. 5. Next Steps: • Disable or Update Plugins: Disable third-party plugins that may use AI features. Update all plugins to the latest versions. • Reinstall Logic Pro: Ensure your installation of Logic Pro 11.1.2 is not corrupted. • Check macOS Updates: Ensure macOS 15.3 is up-to-date with all security and framework patches. • Safe Mode Launch: Try launching Logic Pro in a clean mode without any additional plugins or custom preferences. • Apple Support: If the issue persists, contacting Apple Support with this report could help, as the problem involves their CoreML and Metal libraries. And this is the first section of the problem report (labeled "translated report:" ------------------------------------- Translated Report (Full Report Below) ------------------------------------- Process: Logic Pro [1541] Path: /Applications/Logic Pro.app/Contents/MacOS/Logic Pro Identifier: com.apple.logic10 Version: 11.1.2 (6162) Build Info: MALogic-6162000000000000~4 (1A87) App Item ID: 634148309 App External ID: 871299242 Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2025-01-23 08:25:02.9869 -0500 OS Version: macOS 15.3 (24D60) Report Version: 12 Anonymous UUID: 6E6746D3-CCE6-2827-48EC-FBAD7D707E67 Time Awake Since Boot: 130 seconds System Integrity Protection: enabled Crashed Thread: 13 Dispatch queue: com.apple.coreml.MLE5ProgramLibrary.lazyInitQueue Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: Logic Pro [1541] I recall yesterday night that I was having a similar problem - last night when I attemped to launch it, it would open but it wouldn't open the usual "recent projects" window. It would just hang, and when I hovered over the menu bar with Logic Pro active, the spinny beachball would appear (all other applications were still responsive and working.) im gonna crash out at this point so if anyone has any help I would be a very happy person. Link to full report

5090 9

Notes not opening on MacBook Air, OS Sonoma Version 14.5 Shows crash info: Crash Information: ------------------------------------- Translated Report (Full Report Below) ------------------------------------- Process: Notes [1041] Path: /System/Applications/Notes.app/Contents/MacOS/Notes Identifier: com.apple.Notes Version: 4.11 (2817) Build Info: Notes-2817000000000000~12 Code Type: X86-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2024-05-24 08:24:52.1116 -0600 OS Version: macOS 14.5 (23F79) Report Version: 12 Bridge OS Version: 8.5 (21P5077) Anonymous UUID: B0E7974D-2E5A-1A7A-FF46-E9A75E5CB9CC Time Awake Since Boot: 760 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000020 Exception Codes: 0x0000000000000001, 0x0000000000000020 Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 Terminating Process: exc handler [1041] VM Region Info: 0x20 is not in any region. Bytes before following region: 4458758112 REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START ---> __TEXT 109c34000-10a245000 [ 6212K] r-x/r-x SM=COW /System/Applications/Notes.app/Contents/MacOS/Notes Kernel Triage: VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter

276 1

Logic Pro X crashes after minutes after I quit it

Similar questions