Logic Pro Keeps Crashing: How to Find the Cause

My session quit on me three times in one hour last Tuesday, mid comp on a vocal take for a client deadline. No warning, no beachball, just gone. If Logic Pro keeps crashing on your Mac, don't jump straight to a reinstall. Restart the Mac once and save the newest crash report before you do anything else.

From there, the cause can be a third-party Audio Unit, a specific project, an audio interface, damaged preferences, external hardware, or a bug in Logic Pro itself. This walks through how to separate those possibilities instead of guessing.

Find the Logic Pro Crash Cause in Five Minutes

• Restart the Mac and save the newest .ips or .spin report from Console.
• Hold Option while opening Logic Pro to rule out the last project.
• Use Control, then Don't Launch to test Core Audio and your audio interface.
• Use Control, then Launch Without Audio Units to test third-party plugins.
• If Logic Pro opens normally at every step, isolate the project, interface, or plugin before you touch preferences.

The sections below walk through each of these in more detail, plus what to do if none of them turn anything up.

Why Logic Pro Keeps Crashing in the First Place

Most repeated crashes come from a third-party component, a project-specific trigger, damaged settings, external hardware, or an unresolved Logic Pro or macOS bug. Severe memory pressure can also terminate an app, but confirm that through the crash report rather than assuming every heavy session is crashing from load, since running short on CPU headroom during playback usually shows up as a system overload alert instead, which is a different problem with a different fix. Logic Pro 12.3 included eight specific fixes for cases where Logic could quit unexpectedly, so checking the release notes is worth doing before assuming every crash comes from your own setup.

Most tutorials tell you to update everything and hope for the best. That's backwards. Save a copy of the current crash report before you change anything. Updating Logic or a plugin won't normally erase a report that's already been written, but keeping the original gives you a clean before-and-after comparison once you've updated.

Third-party Audio Units are among the easiest of these to confirm, once you know where to look in a crash report.

How to Read a Logic Pro Crash Report in Console

When Logic Pro crashes outright, meaning it closes completely, macOS normally creates a full .ips report that appears in Console. The report can be missing or incomplete after a forced shutdown, a system-level failure, or other atypical scenarios, so treat its absence as inconclusive rather than as evidence that nothing crashed. A hang is different. If Logic stays open but stops responding, showing the spinning wait cursor, check Spin Reports instead of Crash Reports. A hang and a crash need different evidence, so treating them the same way sends you looking in the wrong place.

Open Console from Applications, then Utilities. For a crash, look under Crash Reports for the newest file starting with Logic Pro. For a hang, check Spin Reports instead.

On an Apple silicon Mac, also check for a report starting with AUHostingServiceXPC at the same timestamp. Third-party Audio Units run in a separate hosting process on Apple silicon, isolated from the main Logic Pro process, so a plugin-related crash sometimes produces its own AUHostingServiceXPC report instead of, or alongside, the main Logic Pro one. Several plugin vendors point users to this process by name in their own support pages, so it's worth checking even if the Logic Pro report doesn't name a specific plugin.

Start with the Exception Type and Termination Reason near the top of the report, then find the Crashed Thread section, then the Last Exception Backtrace if the report includes one. In the crashed thread, frame 0 at the top is the instruction that was running when the process terminated. Lower frames show how that thread got there, so read the block top to bottom, not bottom to top.

A third-party plugin or vendor framework appearing in that backtrace is a lead worth testing, not proof by itself. It could be the direct cause, or it could just be calling into an Apple framework where the actual bug lives.

I once chased a crash for a full week before I started saving every report instead of just the first one. The same vendor framework kept showing up in the same spot in the crashed thread across three separate reports from the same reproducible action. That repetition made the plugin the main lead. Removing it from a copy of the project and reproducing the same action without a crash is what confirmed the diagnosis.

Logic Pro Keeps Crashing on Launch: Four Startup Modes to Isolate the Cause

If Logic Pro crashes before you're even looking at a project, four startup key combinations narrow down the cause fast. Quit Logic Pro completely, then try these in order the next time you open it.

• Open Logic Pro from the Applications folder, then immediately hold Option until Logic opens without its automatic startup action. This skips loading your last project, the Open dialog, or any other action set on the Project Handling pane, which separates an app-level crash from a project-specific one.
• Hold Control, then click Don't Launch in the alert. This opens Logic Pro with Core Audio disabled. If Logic opens cleanly this way, check your audio interface, its driver, or its control software before looking anywhere else.
• Hold Control, then click Launch Without Audio Units. If Logic Pro opens without Audio Units, a third-party plugin becomes a strong suspect, not a confirmed cause yet.
• Hold Shift-Control to open Logic Pro with only Audio Units that already passed validation. This helps when the problem involves a failed validation scan, but it won't exclude a plugin that validated successfully and only crashes during actual use, such as loading a preset, opening its GUI, or during playback.

Launch Without Audio Units, not Shift-Control, is the main test for the plugin hypothesis, since it excludes every third-party Audio Unit rather than only the ones that failed validation. Once Launch Without Audio Units points at a plugin, save a copy of the affected project, remove one third-party Audio Unit at a time from that copy, and test after each removal until the crash stops. That's the same isolation process Apple documents, and it's more reliable than guessing based on whichever plugin you installed most recently.

Logic Pro Keeps Crashing With Third-Party Plugins: Isolate and Reset Audio Units

Once the steps above point at a specific plugin, check the manufacturer's compatibility notes and current installer before resetting any of Logic's validation data.

If a plugin still fails validation after updating, open Logic Pro, then Settings, then Plug-in Manager, select the plugin, and click Reset & Rescan Selection. This forces Logic to re-validate that one plugin instead of guessing at the whole library.

If several plugins are missing or validation results stay inconsistent across the library, use Full Audio Unit Reset at the bottom of the Plug-in Manager window instead, then quit Logic Pro and reopen it so it rescans everything from a clean slate.

Only if the problem persists after that should you fall back to Apple's documented last resort: hold Option in the Finder, choose Go, then Library, and open the AudioUnitCache folder inside Caches. Move the files inside that folder to the Desktop rather than deleting the folder itself, then restart your Mac and reopen Logic Pro so it rescans every installed Audio Unit from scratch. This can take a while, and you won't be able to use Audio Unit plugins in any app until the scan finishes.

Logic Pro Crashes Under Heavy Load: System Overload Alerts

A system overload alert is not an application crash. Logic stays open and only playback stops. Open the Performance Meter by double-clicking the CPU meter in the control bar to check whether Processing Threads or Drive I/O hit the limit, then adjust buffer size, sample rate, or freeze the offending track depending on which one maxed out. I cover buffer size and the related latency tradeoffs in my guide to fixing latency in Logic Pro, and Apple's own guide to avoiding system overloads covers sample rate, send effects, and Sampler virtual memory settings beyond that.

Logic Pro 12, Apple Silicon, and Rosetta

If you updated to Logic Pro 12 and started seeing more crashes, the cause might not be a bug at all. Apple's current Logic Pro requirements list macOS 15.6 or later and a Mac with Apple silicon. Logic Pro 12.2's release notes still mention separate fixes for Intel-based Macs and, on a different line, for Logic running under Rosetta, so Apple's own compatibility wording isn't fully consistent between its product page and its release notes. For the full breakdown of what changed, see my Logic Pro system requirements guide.

Rosetta isn't an Intel Mac feature. It translates the Intel code used by an older Audio Unit while Logic Pro itself can continue running natively. Apple's own guidance is that you can use Intel-only Audio Units on Apple silicon simply by having Rosetta installed on the Mac, since Logic only recognizes those plugins once Rosetta is present. Running Logic Pro itself under Rosetta is a separate setting, and Apple says you shouldn't normally need it. The main documented exception is ARA plugins, such as Melodyne in ARA mode, since native Logic Pro on Apple silicon doesn't currently support ARA.

Logic Pro 12.2 shipped two fixes aimed at Rosetta specifically: one for a crash when zooming on Intel Macs or in Rosetta mode, and another for Logic hanging on launch while running under Rosetta. Those are fixes to Logic Pro's own code in Rosetta-related configurations, not evidence that a plugin is at fault. If Logic Pro is currently set to Open using Rosetta, check Get Info on the app and turn that off unless an ARA plugin specifically requires it, and make sure you're on the latest Logic Pro build either way.

Reset Logic Pro Preferences to Fix Persistent Crashing

If the crash only happens with a control surface, Logic Remote, EuCon device, or MIDI controller connected, start there. Quit Logic Pro, then in Finder choose Go, then Go to Folder, and enter ~/Library/Preferences. Move com.apple.logic.pro.cs into a new folder rather than deleting it, then restart your Mac. You may need to add a standard control surface again inside Logic Pro, and Logic Remote will prompt you to reconnect. EuCon devices don't need to be added again inside Logic Pro. This is a completely separate file from Logic's main preferences, so it won't get touched by the steps below.

If Logic Pro crashes across every project you open, not just one, and no control surface is involved, go to Logic Pro, then Settings, then choose Reset All Settings Except Key Command Assignments. This resets your Control Bar layout, track header defaults, and other app-wide preferences without touching projects, presets, or patches.

If that doesn't help, a damaged main preferences file is the next suspect. Before resetting it, save your custom key commands: go to Logic Pro, then Key Commands, then Edit, then File, then Export. Quit Logic Pro, then in Finder choose Go, then Go to Folder, and enter ~/Library/Preferences again. Find com.apple.logic10.plist for the one-time purchase version, or com.apple.mobilelogic for the Apple Creator Studio version. Move that file into a new folder rather than deleting it, in case you need it back, then restart your Mac.

Check the Latest Logic Pro Release Notes

Before spending an afternoon troubleshooting, check whether Apple already fixed your exact crash. Back up your current Logic Pro app and your projects before installing any update, in case something in a new build doesn't agree with your setup.

Logic Pro 12.3, released in June 2026, fixed eight specific quit-unexpectedly bugs: updating a Smart Tempo Multitrack Set after deleting an audio file, typing into the Step Sequencer's velocity randomization fields, dragging an audio region with a missing file onto the global Harmony track, drag animations in general, importing a PNG into the Alchemy additive editor, Audio Unit scanning, holding Option-X, and opening the Undo History window.

If your crash matches one of those descriptions, update to Logic Pro 12.3 or later and retest before changing anything else. Apple lists those cases as resolved, though a similar-sounding symptom can still have a different underlying cause, such as a third-party plugin or a damaged project. Check Apple's Logic Pro release notes first either way, since whatever version ships after 12.3 will carry its own list of fixes.

Logic Pro Still Crashing? Test With a New Project and User Account

If nothing above stops the crash, isolate whether it's your project, your account, or Logic Pro itself. Create a new empty project with Shift-Command-N, add a couple of Apple Loops, and try to recreate the exact action that triggered the crash. If the new project doesn't crash, the problem is project-specific, not necessarily damage to the project file itself. It could be one plugin inside that project, a specific audio file, an automation lane, or a project setting.

Next, test in a new macOS user account. Create one from System Settings, then Users & Groups, log in, open Logic Pro, and repeat the same action. If it doesn't crash there, something in your main account becomes the main suspect: user-level settings, preference files, plug-in authorization data, templates, or control-surface preferences in the original account, rather than Logic Pro itself.

If the crash also happens in a new project and a new user account, the problem is no longer limited to one project or your main account's preferences. Continue by disconnecting external devices, testing with your Mac's built-in audio instead of an interface, and disabling system-wide Audio Units before concluding you've found an Apple bug. Reinstalling Logic Pro is still a valid step in Apple's own troubleshooting sequence at this point, not something to skip.

If you've worked through all of that and the crash still reproduces, report it through Apple's Logic Pro feedback form, or contact Apple Support directly if you need an active case. Include your Logic Pro version, macOS version, Mac model, exact reproduction steps, and the .ips report, and check my guide to fixing Logic Pro not recording audio if the crash coincides with recording specifically, since a few of the same fixes overlap.

Logic Pro Crashing FAQ

Why does Logic Pro keep crashing on my Mac?

A crash report can narrow the search, but it rarely proves the cause on its own. Common underlying causes include an incompatible or damaged third-party Audio Unit plugin, a project-specific asset such as a corrupted audio file, an external audio or MIDI device, damaged app-wide or user-level settings, or an unresolved macOS or Logic Pro bug. A genuine system overload, where Logic stays open and only playback stops, is a separate issue with its own fix.

Does resetting Logic Pro preferences fix crashing for good?

It fixes crashes caused by damaged or problematic app-wide settings. It doesn't fix an incompatible plugin, an audio interface problem, a project-specific trigger, or a genuine application bug, so treat it as one diagnostic step among several rather than a universal cure.

Why does Logic Pro crash only in one project?

If a new empty project doesn't crash but your original one does, the trigger is project-specific: a corrupted audio file, a specific plugin instance, an automation lane, or a project setting. The underlying bug could still be inside Logic Pro itself; it's just only surfacing at that particular project state. Testing with a copy of the project and removing elements one at a time is the most reliable way to isolate it.

How do I find which plugin is crashing Logic Pro?

Open the newest crash report in Console and check the Crashed Thread section. Frame 0 at the top shows what was running when Logic terminated, and a third-party plugin or vendor framework near that frame is a strong lead. Confirm it by comparing multiple reports from the same reproducible crash, or by removing plugins one at a time from a copy of the project.

Should I reinstall Logic Pro if nothing else works?

Reinstalling is a normal part of Apple's own troubleshooting sequence, not a last resort you skip until you're certain of an Apple bug. If a new project and a new user account both still crash after disconnecting external devices and disabling system-wide Audio Units, reinstalling Logic Pro is a reasonable next step.

Tested with Logic Pro 12.3 on macOS 15.6 on an Apple silicon Mac. Startup modifiers, preference file paths, and the release notes referenced above were rechecked on July 19, 2026.

Related guides: Logic Pro System Overload: How to Find and Fix the Cause · Logic Pro Plugins Not Showing Up: AU Validation Fixes · How to Back Up Logic Pro Projects

Sources: If Logic Pro for Mac isn't working — Apple Support · Logic Pro for Mac release notes — Apple Support