A macOS app that stops responding will not give up the ghost by clicking the
red traffic-light close button. The window stays open, the menu bar stays
frozen, and your work is trapped behind a colored wheel that just spins.
This happens to everyone who has used a Mac for more than a few months, and
most people have one default escape hatch they reach for, then a long list
of workarounds they do not know about.
The official escalation path on macOS for a stuck app has five levels,
ordered from the gentlest to the most destructive. Knowing which level to
use takes about a minute to learn and saves you a forced reboot the next
time your window manager or your browser stops talking to the system.
Why a normal quit fails before you ever see Force Quit
Most apps on macOS run an event loop, a loop that processes user clicks,
network responses, and redraws in sequence. When that loop is busy on a
long task (a video export, a SQL query that touches millions of rows, a
badly written recursive function), the app stops draining events from
the queue. The clicks you send never get processed because the loop has
not looped back to the front of the line.
That is why the red close button does nothing. Closing a window sends a
“please quit” message into the event queue, and the queue is already
backed up behind whatever long task is taking the loop hostage. The app
is not ignoring you. It has literally not had time to look at your
message.
Force Quit (a term Apple uses for the unconditional close path) bypasses
the event queue. The system tells the kernel to send SIGKILL to the
process, the kernel tears it down, and the window vanishes. There is no
graceful save, no “do you want to save this document” prompt, and no
chance for the app to flush its write buffers.
Apple’s documentation recommends waiting 30 to 60 seconds before treating
an app as stuck, which lines up with the event-queue explanation. A long
task on a slow machine can saturate the event loop for a full minute
without being broken. The “Force Quit now” reflex is sometimes a reflex
against a normal slowdown, and the consequence is unsaved work in apps
that do not auto-recover.
The five escape hatches, from gentle to nuclear
These are the five paths macOS gives you when an app is not responding.
Start at the top and work down only when the level above failed.
- Give the app another minute. Not a method so much as a discipline.
- Press
Command + Option + Escapeto open the Force Quit panel. Pick the app. Click Force Quit. - Hold
Option, right-click the app’s Dock icon, click Force Quit in the menu. - Click the Apple menu, pick Force Quit, pick the app in the panel.
- Open Terminal and run
killall AppName(quote two-word apps like"Microsoft Word").
There is a sixth path macOS users occasionally find by accident:
Activity Monitor. Press Command + Space, type Activity Monitor, and
press Return. The window shows every process on the system, including
background helpers and kernel extensions that the Force Quit panel
deliberately hides. Click the CPU or Memory tab and sort by the percent
column to surface the process consuming the most resources, then click
the X-in-a-circle button at the top of the window to terminate it.
Activity Monitor is the right tool when the stuck thing is not an app
at all but a system service or a background helper from another vendor.
The version of this problem where nothing responds
When the entire Mac feels frozen and the keyboard is the only thing still
working, the five-method escalation path above is not enough. The Force
Quit panel needs the Finder to be alive, and if Finder is the stuck
process, you are stuck. Apple offers two further escape hatches for this
case, and the right one depends on whether the system is partially
responsive or fully frozen.
For partial freezes where the keyboard still works, press Control + on desktops or
Command + PowerControl + Command + Touch ID on
MacBooks that have Touch ID in the power button. This sends a “please
restart gracefully” signal to the system. All running apps are told to
save and quit, the system unloads cleanly, and the Mac reboots without
losing the write buffers that a hard shutdown would skip. This is the
gentlest option for partial freezes.
For full freezes where the keyboard is also unresponsive, hold the
power button for about ten seconds. The Mac powers off without warning,
without saving anything, and without waiting for apps to clean up. When
you press the power button again to turn the Mac back on, the boot
process runs as if the previous session never ended. This option is
destructive. Any file the system was in the middle of writing can be
lost or corrupted. The alternative is a Mac that does not respond at
all, so the choice is rarely a real choice.
After the system is back up, run through the post-restart checks below
before assuming the freeze will not repeat.
Post-restart checks that prevent the next freeze
A full-system freeze is rare enough that two in a row usually points to
something specific. Walking through this list catches the obvious
causes.
- Update macOS. Apple menu, then System Settings, then General, then Software Update.
- Update the app that froze through the App Store or the vendor’s website.
- Reopen apps that were running and click Restore on any auto-recovery prompt.
- Run Disk Utility First Aid on your startup disk (Spotlight opens it).
- Disconnect external peripherals and reconnect them one at a time to find the offender.
- Check Login Items. Apple menu, then System Settings, then General, then Login Items.
Trade-offs
Force Quit is the right tool for a stuck window but the wrong tool for
a busy window. The line between a slow app and a stuck app is fuzzy, and
you will sometimes force-quit a task that was about to finish on its
own. After a few false positives, you will start waiting the full 30 to
60 seconds before reaching for the shortcut, and that patience will save
you work you did not realize was about to complete.
Activity Monitor is more powerful than the Force Quit panel because it
can reach system processes the panel hides. That same reach makes it
easy to kill something you did not mean to kill. A user unfamiliar with
the process list can end a critical macOS background service and force a
restart they did not want. Treat Activity Monitor as a power tool with
the safety off, and stick to the Force Quit panel unless you specifically
need to reach a process the panel hides.
The graceful-restart shortcut (Control + Command + Power) is the
gentlest recovery path for partial freezes, but it depends on the
keyboard being alive. When the keyboard is the part that stopped
responding, holding the power button is the only option left, and the
cost is whatever was open across all of your apps at the moment of the
freeze. Back up your open documents on a regular cadence and this cost
shrinks dramatically; skip backups and one bad freeze can cost a day of
work.