Fix 'Your System Has Run Out of Application Memory'

When “Your system has run out of application memory” appears, save anything that still responds, then look for a user app you recognize that is unresponsive or whose memory use keeps growing. Try a normal Quit first. If the Mac remains usable, open Activity Monitor, click Memory, and sort by the Memory column before you force quit anything. Restart if memory pressure does not recover, and check the startup disk if it is nearly full.

That order matters. The warning is about memory available to running apps, not a request to delete random files or terminate unfamiliar macOS processes.

Quick Answer: Recover Without Guessing

1. Save responsive documents. Force Quit can discard unsaved changes.
2. Check the warning window. Note any recognized user app with unusually high memory use, then confirm whether it is stuck or keeps growing.
3. Quit that app normally if possible. Use Force Quit only when it will not respond.
4. Open Activity Monitor > Memory. Sort by Memory and check the Memory Pressure graph.
5. Restart if pressure stays high. Then update the app and macOS before reopening the same workload.
6. Check startup-disk space. macOS uses the startup disk for swap, so a nearly full disk can make memory pressure harder to manage.

Do not start by running a cache cleaner, deleting swap files, or force-quitting every process with a large number beside it. Those actions can create a second problem without identifying the first one.

Step 1: Save Work Before You Force Quit Anything

Preserve what is still responsive first. The warning itself often remains usable even while another app is struggling.

1. Switch to any document, project, or editor that still responds.
2. Save with Command-S.
3. Close tabs or windows you no longer need with their normal controls.
4. Try Command-Q in the suspected app before using Force Quit.

If the entire interface is frozen, you may not get a clean save. But when even one document still responds, take those few seconds. Apple explicitly warns that Force Quit can lose open-file data.

Tip: The biggest number in the warning is a clue, not permission to kill an unknown process. Start with a regular app you recognize—a browser, editor, game, or creative tool.

Step 2: Find the App Using the Memory

Use the warning for immediate triage, then Activity Monitor for context. An obvious user app consuming far more memory than the others is a clue. If it still responds, save and try its normal Quit command; if the Mac is responsive enough to investigate further, open Activity Monitor:

1. Press Command-Space.
2. Type Activity Monitor and press Return.
3. Click Memory.
4. Click the Memory column to sort from highest to lowest.
5. Watch the list for 20–30 seconds. A process whose memory keeps climbing is more suspicious than one stable app using a lot of RAM for a real job.

Apple’s Memory pane guide separates several numbers that are easy to confuse:

The Memory Pressure graph is the best first signal. Apple’s current RAM guidance describes green as efficient memory use, yellow as a warning that more RAM may eventually be needed, and red as a need for more RAM. For one sudden incident, I would first close the runaway user app and see whether the graph recovers. A red spike does not tell you which app is at fault, and it does not prove that deleting files will fix the workload.

Tip: Do not chase “free RAM” as a goal. Apple notes that unused memory does not automatically improve performance; macOS deliberately uses available RAM for active work and caching.

For a fuller walkthrough of the tabs and process list, use the Activity Monitor guide.

Step 3: Quit the Offending App Safely

Quit the identified user app before touching background services. In Activity Monitor:

1. Select the app or its clearly named helper process.
2. Click the Stop button in the toolbar.
3. Choose Quit first.
4. Choose Force Quit only if Quit fails and you accept the risk to unsaved work.

Apple says normal Quit lets the process exit when it is safe. Force Quit ends it immediately and can affect open files or other processes that depend on it.

Browsers deserve one extra check. A single tab, extension, or helper can be the real offender even when the warning names the browser as a whole. Close the heaviest tab or window first if the browser still responds. If it does not, quit the browser and reopen only the tabs you need.

Avoid force-quitting processes you do not recognize. kernel_task, WindowServer, security agents, audio drivers, sync services, and hardware helpers may be doing legitimate system work. If the process name is unfamiliar, record it and investigate after the Mac is stable.

Tip: If you only need the quickest app-only dialog, press Command-Option-Escape. The detailed Force Quit guide explains when to use that window instead of Activity Monitor.

Step 4: Restart, Then Update the Repeat Offender

Restart when pressure does not settle after the app closes. A restart clears the current process state and swap workload, giving you a clean baseline. Save what you can, choose Apple menu > Restart, and wait before reopening every previous app at once.

After the restart:

1. Open only the app that was using excessive memory.
2. Recreate the workload gradually.
3. Watch whether its memory rises continuously again.
4. Install the app’s current stable update.
5. Check System Settings > General > Software Update for a compatible macOS update.

Apple’s app troubleshooting guidance recommends force quitting, restarting, checking compatibility, and updating software. If the same app repeatedly climbs until the warning returns, report the app version, macOS version, workload, and Activity Monitor observation to its developer. That evidence is more useful than saying the Mac “ran out of RAM.”

Step 5: Check Startup-Disk Space Without Confusing It with RAM

A nearly full startup disk can worsen the incident because swap lives there. Activity Monitor reports Swap Used as space used on the startup disk to move data to and from RAM. That does not make storage and memory interchangeable; it means macOS needs both working RAM and enough disk headroom for its memory-management strategy.

Open Apple menu > System Settings > General > Storage and let the category calculation finish.

If the disk is nearly full, remove or move files you understand: old downloads, large exports, obsolete installers, and items already backed up. Empty Trash only after reviewing it. Apple’s storage guide describes the built-in recommendations.

There is no universal free-space number that guarantees this warning will disappear. The amount of swap a workload needs varies, so I would avoid rigid “keep exactly X GB free” rules. The Mac storage guide is the safer next step if the storage bar is close to full.

Step 6: Watch for Memory Pressure Before It Becomes an Emergency

Activity Monitor is ideal during an incident; a persistent monitor is more convenient between incidents. Sensei 2 can put configurable system panels in its menu-bar monitor and dashboard, including memory information alongside CPU, storage, sensors, and other context.

As of August 23, 2026, the current Sensei release is 2.1.2 and requires macOS 14 or later. Sensei can keep memory usage visible with other system readings, but it does not repair a memory leak or magically “reclaim RAM.” The fix is still to close or update the offending app, reduce the workload, restart when necessary, and address low startup-disk space.

Unsafe “RAM Fixes” to Skip

Skip any fix that changes system state before it identifies the cause. In particular:

• Do not delete swap files. macOS manages them; manual deletion can destabilize the running system.
• Do not run sudo purge from a copied command. Clearing caches does not repair a leaking app and can make the Mac slower while data rebuilds.
• Do not terminate every high-memory process. A large, stable allocation may be appropriate for the current job.
• Do not use cache cleaning as emergency RAM recovery. Disk caches and application memory are different resources.
• Do not promise yourself “no data loss.” Any forced exit can discard unsaved changes.

The useful sequence stays simple: save, identify, quit safely, restart if needed, then investigate recurrence.

Stabilize the Mac, Then Find the Pattern

The warning is urgent, but the safest response is measured: save what still responds, close the identified user app, check Memory Pressure, and restart if the system does not recover. Check storage only because the startup disk supports swap—not because deleting random files creates RAM.

If the problem returns, note which app grows, what you were doing, and whether memory pressure rises with it. That turns a frightening popup into a specific issue you can update, report, or avoid.

Optimize Your Mac with Sensei

Monitor performance, clean storage, and manage Mac maintenance in one native app, with a full 7-day trial before you decide.

Download Free TrialView All Plans

Related Guides

• How to Open Task Manager on Mac
• How to Force Quit an Application on Mac
• How to Check Mac Storage
• Why Is My Mac So Slow?