"Your System Has Run Out of Application Memory"

The dialog appears, lists your open applications, and asks you to force quit some of them. It is a memory error. What it doesn't tell you is that macOS treats RAM and disk as one system, and the failure is often on the disk side.

How macOS handles memory pressure

When physical RAM fills, macOS does two things before it gives up. First it compresses inactive memory in place, which typically buys a substantial amount without touching the disk. Then it pages memory out to a swap file in /private/var/vm.

Swap grows dynamically. It needs free disk space to grow into. If the drive is nearly full, macOS can't extend swap, has nowhere left to put anything, and throws this error even when the underlying problem is storage rather than RAM.

Diagnosing it properly

1. Check free disk space first

In Terminal:

df -h /

Use the Avail column rather than what Finder reports, since Finder counts purgeable space as free and macOS can't always release that fast enough. Below roughly 10 to 15 percent free, treat storage as the prime suspect.

2. Check memory pressure, not memory used

Open Activity Monitor and go to the Memory tab. Ignore how much RAM appears used, because macOS deliberately uses all of it. The graph at the bottom is what matters. Green means fine. Yellow means constrained. Red means you're out.

3. Look for one process, not many

Sort by Memory in Activity Monitor. A normal machine shows a gentle curve. A leaking process shows one entry consuming many gigabytes more than everything else, and it climbs steadily while the Mac sits idle.

Browsers are the usual suspects, though the culprit is usually one specific tab or extension rather than the browser itself. Safari and Chrome both have their own task managers that break usage down per tab.

The fixes, in order

1. Free disk space if you're under about 15 percent. This resolves the error outright more often than people expect.
2. Restart. It clears swap, releases leaked memory, and resets the sleep image. Two minutes, and it is the fastest test of whether something was leaking.
3. Quit the specific offender found in Activity Monitor rather than force quitting everything the dialog listed.
4. Cut browser tabs and extensions. Extensions in particular run in their own processes and leak more often than pages do.
5. Add RAM only if pressure sits yellow or red with a healthy amount of free disk. On Apple silicon this means a new machine, so confirm the diagnosis before concluding it.

Freeing up memory without buying anything

If you want to free up memory on a Mac or MacBook right now, in order of what works: quit the process at the top of Activity Monitor's Memory tab, close browser tabs and disable extensions you don't use, restart to clear leaked memory and swap, and make sure the disk has room for swap to grow. That last one is the step people skip.

What won't help

Memory cleaner utilities that promise to free RAM work by forcing macOS to purge caches it deliberately kept. The number in the graph improves, then macOS reads the same data back from disk moments later. You have converted free memory into disk activity, which is the opposite of what you wanted.

macOS is already managing memory well. The genuine problems are a specific leaking process, or no room for swap.

If it keeps coming back

A recurring error with plenty of disk space and green memory pressure points at a leak. Note which application is at the top of Activity Monitor's memory list when the dialog appears, since that's the culprit far more often than the app that happens to be in front of you.

Persistent leaks after an update are usually a bug in that specific version. Updating, or rolling back, resolves more of these than any amount of cleaning.