Sweepfor Mac

Troubleshooting

Mac Out of Memory Warning? Here's What's Actually Happening

Mac says it's running out of memory? Here's how memory pressure actually works on macOS, what triggers warnings, and how to read Activity Monitor.

8 min read

The fans wind up, the cursor turns into a beach ball every few seconds, Slack is laggy, Safari is dropping frames. You open Activity Monitor and the Memory Pressure graph at the bottom is red. Or worse, the dialog appears: “Your system has run out of application memory.” On the surface, your Mac says it’s out of RAM. The truth is more layered than that.

Understanding what macOS calls “memory” — and what causes the warning — saves you from solving the wrong problem.

How memory works on macOS

Modern macOS uses three types of memory storage and shuffles data between them constantly:

  • Wired memory — kernel and driver code that can’t be swapped out. Generally 1.5–4 GB.
  • App memory — the working set of running apps. Active code and data.
  • Compressed memory — older app memory that the kernel has compressed in-place to make room. Still in RAM, just half the size.
  • Cached files — disk content kept in spare RAM for fast re-reads. Released on demand.
  • Swap used — overflow that didn’t fit in RAM, written to your SSD.

The total is called Memory Pressure, and it’s the only number you should care about. macOS shows it as a colored graph at the bottom of Activity Monitor’s Memory tab:

  • Green — plenty of headroom. Don’t worry.
  • Yellow — under load but coping. Compressed memory is doing work.
  • Red — system can’t keep up. This is when warnings fire.

The “out of memory” warning doesn’t mean RAM is at zero. It means the rate of memory demand exceeds what the kernel can satisfy via compression and swap.

Read Activity Monitor like a pro

Open Activity Monitor (Cmd+Space → type “Activity Monitor”). Click the Memory tab.

Top of the window: list of processes by memory use. Sort by the Memory column descending.

Bottom of the window:

  • Memory Pressure — the colored graph.
  • Physical Memory — your installed RAM.
  • Memory Used — wired + app + compressed.
  • Cached Files — size of disk cache. Looks scary, ignore it.
  • Swap Used — overflow. Should be near zero ideally; under 2 GB is fine.

A healthy 16 GB Mac with light use shows: Memory Used around 6–9 GB, Cached Files 4 GB, Swap Used near 0, Pressure green.

Trouble looks like: Memory Used 14 GB, Cached Files 200 MB, Swap Used 8 GB, Pressure red.

What’s actually using your memory

Click the Memory column header to sort. The top entries usually include:

  • Google Chrome — each tab is roughly 100–500 MB. With 30 tabs, you’re at 5+ GB.
  • WindowServer — the macOS GUI process. Normal: 200 MB to 1 GB. Higher means a graphics leak; restart fixes it.
  • kernel_task — kernel itself. Normal: 1–2 GB. Higher with kernel extensions running.
  • Slack / Discord / Teams — each holds 600 MB to 1.5 GB.
  • Safari — quite frugal compared to Chrome. Each tab is its own process via the Memory column.
  • mds / mds_stores — Spotlight indexing. Spikes during indexing, normal otherwise.
  • com.apple.WebKit.GPU — GPU process for web content.

Click the small “i” button on a process to see detailed memory breakdown. The “Real Memory” number is what’s actually consuming RAM. “Virtual Memory” is the address space, often huge but mostly unused.

Diagnose AND clean in one appSweep finds the buildup behind the error and clears it. Try Sweep free →

Why warnings happen even on 32 GB Macs

A common assumption: “I have 32 GB, I should never see memory warnings.” Wrong, for three reasons:

  1. Workloads scale with RAM. People with more RAM open more tabs, run more apps, edit larger files. A photographer on a 32 GB Mac with Lightroom processing 60 MP RAW files in batches of 200 will hit the same wall.
  2. Memory leaks ignore your RAM size. A leaking Electron app eats 100 MB/hour whether you have 8 GB or 64 GB. Eventually it fills up.
  3. Swap depends on disk space. If your SSD is 95% full, swap can’t expand and the warning appears at far less actual memory demand.

When to actually worry

Not every yellow Memory Pressure reading is a problem. The signs that warrant action:

  • Pressure is red for several minutes at a stretch, not just spikes.
  • The Mac feels sluggish: cursor lag, beach balls, slow window switching.
  • Swap Used exceeds 5 GB consistently.
  • A specific process keeps growing unbounded.
  • Memory warnings appear within an hour of restart.

If pressure occasionally hits yellow during a Photoshop export and clears immediately, that’s normal. The system is using its tools.

Quick fixes when the warning hits

  1. Quit the top memory user. Activity Monitor → click the X button in the toolbar with the offender selected → Force Quit.
  2. Close browser tabs. Aggressively. Bookmark first if you want to come back.
  3. Quit messaging apps when not actively chatting. Slack and Teams idle at 1+ GB.
  4. Restart the Mac. Clears all swap, all leaked memory, all compressed pages.
  5. Free disk space. If your SSD is under 10% free, swap is constrained. Empty Downloads and Trash, then watch swap recover.

Free up disk in one clickMany errors stem from a full startup disk. Sweep finds gigs of cruft fast. Get Sweep free →

Find a leaking app

If the same app keeps growing after restart, it has a leak. To prove it:

  1. Restart the Mac so memory is clean.
  2. Open Activity Monitor → Memory tab → sort by Memory.
  3. Note baseline numbers for the suspect.
  4. Use the app normally for an hour.
  5. Compare. A leak shows steady growth without ever shrinking.

What to do with a leak:

  • Update the app — most leaks get patched within a release or two.
  • File a bug with the developer if it’s a recent build.
  • Restart the app every few hours as a workaround.
  • If it’s a critical work tool, look for an alternative.
Tip: Activity Monitor's "CPU TIME" column shows cumulative CPU usage since launch. A high number on an app you barely use means it's been busy in background — a leak indicator.

Reduce baseline memory pressure

These changes reduce how much RAM your Mac uses idle.

1. Trim login items

System Settings → General → Login Items. Disable apps you don’t need at startup. Each Electron app saves you ~500 MB.

2. Quit cloud sync clients when not syncing

Dropbox, Google Drive, Box, OneDrive each consume 300–800 MB. If you don’t need real-time sync, quit them.

System Settings → Siri & Spotlight → Spotlight Privacy → add external drives or volumes. Each indexed volume keeps RAM allocated.

4. Reduce open browser tabs

Keep frequent sites bookmarked. Use a tab suspender extension. Use Reader Mode for long articles you’ll come back to.

5. Choose lighter app variants

  • Use Apple Mail instead of Outlook desktop where possible.
  • Use Slack in a tab instead of the desktop app.
  • Use Notion in a tab instead of the desktop app (or the iOS app on a separate screen).

When the answer is more RAM

Some workloads simply need more RAM than your Mac has. Indicators:

  • You routinely keep one app open that needs more than half your total RAM (Logic, Final Cut, Lightroom Classic, Xcode building large projects, virtual machines).
  • Memory Pressure spends most of the workday in red.
  • Swap consistently exceeds 10 GB.
  • You’re considering a Mac upgrade anyway.

If you’re on an 8 GB M1/M2 Mac and you’re a developer or creative, 16 GB is the floor. 24 or 32 GB is more comfortable. Apple Silicon RAM is unified and not user-upgradeable, so this means buying a different Mac.

When kernel_task is the issue

If kernel_task is using 5+ GB:

  1. Disconnect external displays and accessories.
  2. Restart with no peripherals attached.
  3. If kernel_task is still huge, suspect a kernel extension. System Settings → Privacy & Security → System Extensions. Disable third-party kexts.
  4. Boot into Safe Mode (hold Shift on Intel; on Apple Silicon, hold power, choose drive, hold Shift, click Continue in Safe Mode). If kernel_task is normal in Safe Mode, a kext is the culprit.

When pressure is permanent

A Mac that runs in red Memory Pressure for hours every day with no leak you can find is undersized for the work you do on it. No amount of cache clearing fixes that. Your options:

  1. Reduce workload — fewer tabs, fewer concurrent apps.
  2. Add RAM if your Mac supports it.
  3. Replace the Mac with one that has more RAM.

Memory pressure is a useful signal, not a death sentence. Most yellow readings are macOS doing its job — compressing, swapping, juggling — and aren’t a problem at all. Red pressure plus actual sluggishness is the only warning that demands action.

← Back to all guides