FIX macOS System Memory High with Chrome Open (2026)

Key takeaways

• macOS logs Chrome’s GPU compositing memory under “System”, not under Chrome, so the cause looks invisible in Activity Monitor.
• Discarding inactive tabs removes their GPU allocations entirely, unlike compression which still keeps them in the System pool.
• Yellow Memory Pressure? Go to chrome://discards/ and discard idle tabs. This often returns the gauge to green immediately.

You open Activity Monitor expecting to blame Chrome directly, but Chrome’s number looks reasonable — it’s the “System” category that’s eating 10 GB. This is a common source of confusion. macOS accounts for GPU buffers, kernel caches, and hardware-acceleration memory under System rather than attributing it to the Chrome process. The more tabs Chrome has open with hardware acceleration active, the larger that System figure grows.

Quick Diagnosis

Fix 1: Check Memory Pressure in Activity Monitor

Activity Monitor’s Memory Pressure gauge is more meaningful than raw memory numbers for diagnosing whether action is needed.

1. Open Activity Monitor (Applications > Utilities, or Spotlight search for “Activity Monitor”).
2. Click the Memory tab.
3. Look at the Memory Pressure graph at the bottom.
   • Green: macOS has sufficient memory. No action required.
   • Yellow: macOS is compressing memory. Performance may degrade soon.
   • Red: macOS is writing to SSD swap. Performance is already degraded.
4. Also check the Swap Used figure. Non-zero swap alongside high System memory confirms RAM is insufficient for current usage.

Fix 2: Discard Inactive Chrome Tabs

Suspended tabs release their renderer process entirely. Unlike inactive tabs that macOS compresses, discarded tabs are removed from RAM — macOS no longer needs to maintain their GPU buffers.

1. In Chrome, go to chrome://discards/ in the address bar.
2. The table shows all open tabs with their current memory state.
3. Click Urgent Discard on any tab you are not actively using.
4. Return to Activity Monitor and watch the Memory Pressure gauge — it should drop as Chrome releases GPU memory.
5. Discarded tabs reload automatically when you click them.

Focus on discarding tabs with heavy visual content: dashboards, video players, design tools, and news sites with auto-playing media.

Fix 3: Close Unnecessary Chrome Windows

Each Chrome window maintains its own compositing layer in macOS. Multiple windows multiply the GPU memory footprint.

1. Count your open Chrome windows — use the Window menu to see all windows.
2. Consolidate tabs from multiple windows into one window: drag tabs from one window to another.
3. Close windows with no active tabs.
4. Check Activity Monitor memory pressure again after consolidating.

Fix 4: Restart Chrome Completely

Restarting Chrome forces macOS to reclaim all GPU memory that Chrome allocated during the session, including memory that Chrome’s own garbage collector has not yet released.

1. Use Chrome menu > Quit Google Chrome (not just closing the window — background Chrome can persist).
2. Confirm in Activity Monitor that no Chrome processes remain in the list.
3. Wait 10-15 seconds before reopening Chrome.
4. After restarting, observe that System memory is lower with the same number of tabs, because fresh renderer processes have not yet accumulated GPU allocations.

Fix 5: Disable Hardware Acceleration

If System memory consistently grows to very high levels even with a moderate number of tabs, hardware acceleration may be allocating more GPU memory than necessary.

1. Open Chrome Settings (three-dot menu > Settings).
2. Search for “hardware acceleration” or go to System in the left sidebar.
3. Toggle off Use graphics acceleration when available.
4. Click Relaunch to restart Chrome with this setting applied.
5. Monitor Activity Monitor System memory over the next 30 minutes.

Note: Disabling hardware acceleration reduces video playback quality and WebGL performance. It is best used as a diagnostic step or for Macs where GPU memory is a known bottleneck.

Reducing Chrome’s Pressure on macOS System Memory

If you’re consistently seeing yellow or red memory pressure with Chrome open, tab suspension is the most direct lever. SuperchargePerformance discards idle tabs via Chrome’s chrome.tabs.discard(), removing their GPU memory allocations from the System pool entirely — unlike inactive tabs that macOS merely compresses. It also blocks ad iframes and tracking scripts at the network level, reducing background rendering that inflates GPU usage.

Active, pinned, and audible tabs are never suspended. If you’re on a Mac with 16 GB or more and only keeping a moderate number of tabs open, you probably don’t need the extension — fixing hardware acceleration (Fix 5) or restarting Chrome periodically is sufficient.

Technical Background

macOS uses a unified memory architecture (especially pronounced on M-series Macs) where CPU and GPU share the same physical RAM. When Chrome opens a tab with hardware acceleration, macOS allocates GPU memory for that tab’s compositing layer. This GPU memory appears under “System” in Activity Monitor rather than under the Chrome process.

macOS manages memory pressure in three stages: first it reclaims inactive app memory, then it compresses RAM pages, and finally it writes to SSD swap. The compression and swap stages require CPU work — on M-series Macs, this shifts load from efficiency cores to performance cores, increasing power draw and heat.

Discarding Chrome tabs removes their GPU allocations from the system pool entirely, reducing compression workload and often bringing the Memory Pressure gauge from yellow back to green without requiring a browser restart.

For related issues, see Fix Chrome Memory Leaks on macOS Tahoe and Fix Chrome High Memory Usage.