How to kill a runaway process on Mac
When an app pegs your CPU or eats all your RAM, you need to kill it fast. Here are the GUI and Terminal ways, plus when to use each.
Something is wedged. A browser tab, a renderer, a stuck Electron app — whatever it is, it’s pinning a core at 100% and your fans are climbing. You want it gone, and a regular Cmd-Q isn’t doing it. Here are the reliable ways to kill a process on macOS.
The fast options
Force Quit (Cmd-Option-Escape)
This is the panic-button shortcut every Mac user should know. It pops a small window listing running apps; pick the offender, hit Force Quit. Works for anything with a Dock icon.
It doesn’t cover background processes, helper apps, or anything without a visible UI — for those, you need one of the next two.
Activity Monitor
Open Activity Monitor, sort by %CPU or Memory, find the rogue, click the X in the toolbar, choose Force Quit. This works on every running process, including the background ones Cmd-Option-Esc won’t show you.
Terminal: kill, killall, pkill
For anything terminal-side or anything that won’t die through the GUI:
- Find the PID:
ps aux | grep ProcessNameorpgrep -fl ProcessName. - Try a graceful stop first:
kill PID. This sends SIGTERM and lets the process clean up. - If it ignores you after a few seconds:
kill -9 PID. SIGKILL — the kernel reaps it immediately. - Want to kill every instance by name?
killall "App Name"orpkill -f pattern.
A note on kill -9: it doesn’t let the process save state, flush buffers, or run shutdown handlers. Reach for kill (no -9) first, only escalate if needed.
Finding the right thing to kill
The hard part is usually identifying the runaway, not killing it. A few approaches:
- Activity Monitor — sort by %CPU, the offender is at the top.
- top -o cpu in Terminal — same idea, faster to launch.
- A menu-bar monitor — best for spotting it the moment it starts, not after you’ve noticed the fans.
Beacon fits this last role. Its menu-bar CPU readout updates roughly once a second, and clicking the icon shows the top CPU users right there.
- Install Beacon and enable the CPU readout in Settings > Menu Bar.
- When CPU spikes, click the icon — you see the top three processes immediately.
- Click a process to jump to it in Activity Monitor for the kill, or grab the PID and use
killin Terminal.
The faster you spot a runaway, the less battery, heat, and time it costs you. The killing part is easy — the noticing is what gets you.
More Beacon tips
-
Better alternatives to Activity Monitor on Mac
Activity Monitor is fine for a one-off check, but it's a window you have to keep finding. Here are faster, ambient ways to see what your Mac is doing.
-
Is your Apple Silicon Mac thermal-throttling?
Apple Silicon throttles less than Intel, but it still throttles. Here's how to tell — and what it costs you when it happens.
-
Comparing Mac system monitors (iStat, MenuMeters, Beacon, etc.)
An honest look at the main menubar system monitors for macOS in 2026 — what each does well, what's frustrating, and how to pick.
-
See CPU usage in your Mac menubar
How to keep an always-visible CPU readout in your menu bar, without leaving Activity Monitor open in the corner of every Space.