FIX Chrome Not Enough Memory to Open Page: 5 Fixes (2026)

Key takeaways

• This isn’t a Chrome crash. The OS refused Chrome’s memory request because the Commit Limit (RAM + pagefile) is exhausted.
• On 8 GB Windows systems, suspending 10–15 idle tabs typically recovers 1–2 GB. Go to chrome://discards/ right now.
• Discord, Slack, and Spotify each run a full Chromium instance. Closing them frees hundreds of MB from the shared Commit pool.

You try to open a new tab and Chrome just refuses — no crash, no Aw Snap, just an error page blocking the load. This is different from an “Aw, Snap!” crash. Chrome actively blocked the new page because the operating system has reached its Commit Limit — the sum of physical RAM plus the pagefile. Chrome asked the OS for memory to render the new page and got a hard refusal.

This is common on 8 GB Windows 11 systems, where the OS itself reserves a significant chunk of RAM before Chrome opens a single tab.

Quick Diagnosis

Fix 1: Discard Background Tabs Immediately

The fastest fix is releasing memory from tabs you are not actively using.

1. Press Shift + Esc to open Chrome Task Manager.
2. Click Memory Footprint to sort by highest usage.
3. For each tab you do not need right now, click the tab in the list and click End Process — the tab reloads when you click it later.
4. Alternatively, go to chrome://discards/ and click Urgent Discard for inactive tabs.
5. Attempt to open the blocked page again — in most cases, freeing 500 MB to 1 GB is sufficient.

Fix 2: Disable Unused Extensions

Extensions run in persistent background pages that consume RAM whether or not you are using them.

1. Go to chrome://extensions/ in the address bar.
2. Disable any extension you do not use daily by toggling it off.
3. Restart Chrome after disabling extensions.
4. Check if the error recurs — if not, one of the disabled extensions was holding significant memory.

Fix 3: Close Electron Apps

Discord, Slack, Spotify, VS Code, and other Electron apps are each a separate Chromium browser instance. They each contribute to the system-wide Commit Charge that Chrome’s new-tab requests are competing against.

1. Open Windows Task Manager (Ctrl + Shift + Esc).
2. On the Processes tab, look for Discord, Slack, Spotify, or similar Electron apps under the Memory column.
3. Right-click each one and select End Task, or quit them from their system tray icons.
4. Confirm total memory usage drops in Task Manager, then try opening the Chrome page again.

Fix 4: Restart the Browser

Chrome holds “stale” memory from closed tabs that has not yet been returned to the OS through garbage collection. Restarting Chrome flushes all of this at once.

1. Note which tabs you need (bookmarks or a tab manager can help).
2. Completely quit Chrome — on Windows, right-click the taskbar icon and select Exit to ensure background Chrome processes are stopped.
3. Reopen Chrome and only restore the tabs you need actively.
4. Total memory after a restart should be substantially lower than before.

Fix 5: Increase Windows Pagefile Size

On Windows, the Commit Limit is physical RAM plus pagefile. If the pagefile is too small, Chrome’s memory requests fail even when physical RAM could be supplemented by disk swap.

1. Press Win + R, type sysdm.cpl, and press Enter to open System Properties.
2. Click the Advanced tab, then Settings under Performance.
3. Click the Advanced tab again, then Change under Virtual Memory.
4. Uncheck Automatically manage paging file size for all drives.
5. Select your system drive, choose System managed size, and click Set.
6. Click OK through all dialogs and restart Windows.

After the restart, Windows can expand the pagefile dynamically, raising the Commit Limit ceiling and allowing Chrome to allocate memory for new page loads.

Staying Below the Memory Threshold Automatically

If you regularly hit this error on an 8 GB system, tab suspension is the most practical fix short of buying more RAM. SuperchargePerformance keeps Commit Charge low by automatically discarding inactive tabs before the error threshold is hit. Discarded tabs use near-zero memory and reload when you click them. It also blocks ad iframes at the network level, preventing Subframe processes from inflating the count in background tabs.

Users with 10–15 suspended background tabs typically recover 1–2 GB of Commit Charge — usually enough to eliminate this error on 8 GB systems. If you only keep a handful of tabs open, the built-in Memory Saver in Chrome Settings may be all you need.

Technical Background

The “Not Enough Memory to Open This Page” error is triggered at the OS memory allocation layer, not inside Chrome itself. When Chrome’s renderer process calls the OS to allocate memory for a new page, the OS checks whether the requested amount fits within the current Commit Limit. If it does not, the OS returns an out-of-memory error, and Chrome displays this error page.

This differs from the “Aw, Snap!” crash, which occurs when a renderer that has already been allocated memory exceeds that allocation. The “Not Enough Memory” error is a preventive block — Chrome never starts loading the page. If you are seeing Aw, Snap errors rather than this error page, the cause and fix are different.

The Commit Limit is not fixed — it equals physical RAM plus pagefile size. Increasing the pagefile or reducing active Commit Charge by suspending tabs both resolve the condition.

For related issues, see Fix Chrome Out of Memory Crashes and Fix Chrome High Memory Usage.