'The Application Unexpectedly Quit' on Mac? Here's Why and How to Stop It

You’re three hours into a Logic Pro session and the dialog appears: “The application Logic Pro X quit unexpectedly.” You click Reopen, it crashes again on launch. Or Safari hangs, beach balls, then shows “Safari quit unexpectedly. macOS and other apps are not affected.” The reassurance is cold comfort when your tab session is gone.

This error is macOS telling you a process violated some rule the kernel cares about — usually a memory access it shouldn’t have made — and got terminated rather than allowed to corrupt anything else.

What’s actually being said

The exact text varies by macOS version:

• “The application quit unexpectedly.”
• ” quit unexpectedly. Click Reopen to open the application again.”
• “Problem report for ” with a Report to Apple button

Behind all three is the same event: the app received a signal it couldn’t handle (usually SIGABRT, SIGSEGV, or SIGBUS), and macOS wrote a crash report to disk before the process died.

Read the crash report — it usually tells you the cause

The single most useful step most people skip: actually look at the crash log.

1. Open Console.app (Applications → Utilities → Console).
2. In the sidebar, click Crash Reports.
3. Find the entry matching the app and timestamp.

Look at the top of the report for a few key fields:

• Exception Type — EXC_BAD_ACCESS means memory corruption, often a bad plugin. EXC_CRASH (SIGABRT) is a deliberate abort, often a missing framework.
• Termination Reason — sometimes spells it out: “DYLD, code signing blocked mmap()” or “Code Signature Invalid.”
• Crashed Thread — the stack trace tells you which library was active when it died. If the top frame is a third-party plugin, that’s your culprit.

A line like Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11 with libobjc.A.dylib near the top usually points at incompatible plugins. A Library Validation Failed reason points at a code-signing problem.

Quick fixes from least to most invasive

1. Force quit and relaunch

Cmd+Option+Esc → select the app → Force Quit. If the app is launchd-managed (background services), this may not stick — see step 5.

2. Restart the Mac

Genuinely fixes a surprising number of repeating crashes. macOS keeps shared memory regions alive across app launches; a corrupted region clears on restart.

3. Clear the app’s caches

Quit the app first. Then in Finder use Go → Go to Folder (Cmd+Shift+G) and check:

• ~/Library/Caches/<bundle-id>
• ~/Library/Containers/<bundle-id>/Data/Library/Caches
• ~/Library/Saved Application State/<bundle-id>.savedState

Move (don’t delete yet) those folders to the Desktop. Relaunch. If the app behaves, trash the moved folders.

4. Delete preferences

Sometimes a corrupt plist crashes the app on launch. Quit the app, then move:

• ~/Library/Preferences/<bundle-id>.plist
• ~/Library/Containers/<bundle-id>/Data/Library/Preferences/<bundle-id>.plist

You’ll lose customizations but the app should launch.

5. Kill background helpers

Many apps run helper processes. Open Activity Monitor, search the app’s name, and quit anything you find. Adobe, Microsoft, and Dropbox all spawn multiple background processes that can deadlock.

Diagnose AND clean in one appSweep finds the buildup behind the error and clears it. Try Sweep free →

Specific patterns and their fixes

Crash on launch only

The app dies before its window appears. Almost always:

• A startup plist is corrupt — delete preferences (step 4).
• A login item is auto-loading something incompatible — System Settings → General → Login Items.
• The app needs Full Disk Access to read its own data store and was denied — System Settings → Privacy & Security → Full Disk Access.

Crash after a specific action

Crashes when you save, when you print, when you import a specific file: that’s a data-driven crash. Try the action with a different file. If it survives, the file is corrupt.

Crashes that reference plugins

Audio apps (Logic, Pro Tools, Ableton), DAWs in general, and Final Cut/Premiere have rich plugin ecosystems and the plugins cause most crashes. Test by:

1. Move all third-party plugins out of ~/Library/Audio/Plug-Ins/Components (for AU) or the relevant folder.
2. Launch the host app.
3. Add plugins back in batches until the crash returns.

Crashes with “Code Signature Invalid”

The app’s signature is corrupt or revoked. Re-download the app from the developer’s site or the App Store. Don’t try to patch this — code signing is the layer protecting you from malware.

Crashes after macOS upgrade

This is its own category. The app was built against older system frameworks and the upgraded macOS broke it. Two paths:

• Check the developer’s site for an updated build.
• If they’ve abandoned the app, you may need an alternative.

Memory pressure crashes

Open Activity Monitor → Memory tab → look at Memory Pressure at the bottom. A red bar means macOS is killing apps that grew too large. Browsers, Electron apps, and Chrome in particular hit this on 8 GB Macs. Fix by closing tabs, quitting other apps, and — if the same app dies repeatedly — checking its Memory column to see if it’s leaking.

Don’t reinstall macOS yetSweep clears the buildup that’s actually causing the issue. Free for macOS →

Reset deep state when nothing else works

If clearing caches and preferences didn’t help, fully remove and reinstall the app:

1. Quit the app.
2. Drag the app from Applications to Trash.
3. Hunt down its leftover files: ~/Library/Application Support/<name>, ~/Library/Caches/<bundle-id>, ~/Library/Logs/<name>, ~/Library/LaunchAgents/<plist>, ~/Library/LaunchDaemons/<plist>.
4. Empty Trash.
5. Restart.
6. Reinstall from a fresh download.

Many apps leave a launchd plist that auto-restarts the helper after you “uninstall.” If the app keeps coming back, check launchctl list | grep <name>.

When it’s actually hardware

A few signs the problem isn’t the app:

• Multiple unrelated apps crash with EXC_BAD_ACCESS errors.
• Crashes coincide with kernel panics (gray screen, “Your computer was restarted because of a problem”).
• Apple Diagnostics (hold D at boot on Intel; Apple Silicon: power on, choose Options, then run Diagnostics from there) reports memory or SSD errors.
• The Mac runs hot and the fans spin even when idle, then crashes follow.

If two of those apply, run Apple Diagnostics first, then back up and call Apple Support. RAM and SSD failures masquerade as random app crashes for weeks before they get severe enough to be obvious.

Prevent crashes going forward

• Keep the app updated. Most “unexpectedly quit” bugs get fixed within a release or two.
• Don’t run macOS at 95%+ disk usage. APFS does cleanup work that needs slack space.
• Restart your Mac at least once a week. Long uptime accumulates leaked memory.
• If you use plugins, keep a current list of which versions you have so you can rollback when an update breaks compatibility.

The app crash dialog feels like a dead end, but the crash report under it usually contains the answer. Read the Exception Type, follow the stack trace’s top non-system frame, and you’ll know what to fix in five minutes instead of fifty.