macOS 'Application Not Responding' Fixes That Work

First: Force Quit the Frozen App

When an app stops responding on macOS, the spinning beachball is your first clue. 90% of the time, the app is just stuck. Don't reboot yet. Just kill it.

Press Command + Option + Escape to bring up the Force Quit dialog. Select the app and hit Force Quit. That's it. The app dies, the beachball goes away, and you can relaunch it.

If the dialog doesn't help — the app might be completely hung — use Activity Monitor (in /Applications/Utilities/). Find the process, click it, and hit the X button in the toolbar. Choose Force Quit.

One thing I see all the time: people panic and restart the Mac. Don't. Force quitting is faster and doesn't lose your other work.

Second Most Common: Not Enough RAM or Swap Churning

If you're constantly seeing apps freeze, especially when you have 15 Chrome tabs open plus Photoshop, it's a memory problem. macOS uses swap space on your disk when RAM runs out. When it does, everything grinds to a halt — and apps stop responding because they're waiting on disk I/O.

Check memory pressure in Activity Monitor under the Memory tab. If the graph is red or yellow, you're overcommitted.

The fix here is simple: close tabs, quit apps you're not using, and if you're on a Mac with 8GB of RAM, consider upgrading — if it's a MacBook Pro or iMac, you can often still swap in more memory. On Apple Silicon, you can't upgrade, so you'll have to live with fewer open apps.

Another thing: your disk might be full, and macOS has nowhere to write swap. Check with df -h in Terminal. If your startup disk is over 90% full, that's your bottleneck. Free up space — empty the Trash, move files to an external drive, or use clean up tools like DaisyDisk.

Third: Background Processes and Login Items Hogging the CPU

Sometimes the app that's not responding isn't the problem. It's a background process eating up the CPU. I've seen Microsoft Teams or Dropbox go haywire, consuming 120% of a core, and suddenly your main app can't get any CPU time — so it freezes.

Open Activity Monitor and click the CPU column to sort. Look for anything pegged near 100% that isn't your app. If it's a known culprit like Teams, quit it from the menu bar, then update it. If it's something you don't recognize, Google the process name before killing it — don't nuke random system processes or you'll cause more problems.

Also check your Login Items (System Settings > General > Login Items). The less you have starting at login, the better. Remove anything you don't need — especially old Adobe updaters and Steam.

SMC and NVRAM Resets — When All Else Fails

If apps keep freezing across the board, especially after a macOS update, it might be low-level firmware weirdness. Resetting the SMC (System Management Controller) and NVRAM can clear that up.

For Intel Macs: Reset NVRAM by shutting down, then power on and immediately press Command + Option + P + R for 20 seconds. For SMC, plug in the power, shut down, then hold Shift + Control + Option on the left side and the power button for 10 seconds, then release and power on.

For Apple Silicon Macs: You don't reset NVRAM — it's handled automatically. For SMC, you just shut down and plug in the power. That's it. There's no key combo for SMC on M1/M2/M3.

This is my last resort. Most of the time, it's not needed. But if you've tried everything else and apps are still freezing, it doesn't hurt.

Quick Reference: What to Do When an App Freezes

That's the order I use every time. Force quit first, then look at system health. You'll fix 95% of freezes at step 1. The rest is just knowing where to look.