Chrome Out of Memory? Why It Happens and How to Fix It

Chrome runs out of memory when the tabs, extensions, and background processes you have open all together ask for more RAM than your computer has free. When that happens, Chrome kills the tab, or sometimes the whole browser, rather than letting your entire system lock up. You’ll usually see a crashed tab rather than a polished error message, and it tends to strike at the worst possible moment: forty research tabs open the night before a deadline, or a video call running next to a dozen documents.

This guide walks through why Chrome hits that ceiling, how to fix it the moment it happens, and what to change so it stops happening as often. It also covers the part people worry about most: getting your tabs back afterward, and making sure a future crash never costs you work again.

What Does “Chrome Out of Memory” Mean?

It means a tab, or Chrome’s own processes, asked the operating system for more RAM than was available, so Chrome ended the process rather than let the whole system freeze. Chrome runs each tab and most extensions as a separate process by design, for stability and security, which is exactly what lets it kill one runaway tab without taking down every other tab you have open.

What you actually see varies. Sometimes it’s a single tab going blank with a message that it crashed or ran out of memory. Sometimes the whole browser becomes unresponsive for a moment before closing entirely. Either version has the same root cause: total memory demand crossed a line your system could not support.

Not the same as freezing. An out-of-memory crash kills a tab or process outright. A frozen, unresponsive Chrome window can happen for other reasons entirely, like a stuck script. Our Chrome freeze guide covers that separate set of causes if restarting alone does not fix an unresponsive window.

Here’s a fast way to match your situation to a fix, with the full detail further down this page.

Why Does Chrome Run Out of Memory in the First Place?

Chrome runs out of memory because its multi-process design adds up memory use across every open tab, extension, and internal function, and that total eventually exceeds what your system has free. This isn’t a flaw unique to Chrome; every Chromium-based browser works the same way. The tradeoff is real: process isolation keeps one bad tab from crashing everything else, but it also means memory use scales with how much you keep open rather than staying at some fixed baseline.

A handful of quiet tabs rarely causes this. The crashes cluster around specific combinations: a video call plus several Google Docs plus a dashboard-style site with live charts, all running at once, often alongside a browser that has not been restarted in days. Each tab looks reasonable on its own, but Chrome is not sharing memory across them, it’s adding them up.

Machines with limited RAM hit this ceiling faster and more often. If you’re on a laptop with 8GB or less, the margin for error is genuinely smaller, and our guide on Chrome and 8GB RAM covers realistic tab counts for that setup specifically. On higher-RAM machines, the same crash usually means something more unusual is going on, like one tab with a memory leak or a very large number of extensions running continuously in the background.

How Do I Fix a Chrome Out of Memory Error Right Now?

Restart Chrome first, since that clears every open process and gives memory allocation a clean slate. This is the fastest fix and works in the large majority of cases, because most out-of-memory crashes come from an accumulated combination of tabs and extensions rather than one single unfixable problem.

1. Close and reopen Chrome. If Chrome will not close normally, use your operating system’s own task manager to end the process, then relaunch.
2. Do not reopen everything at once. Open your most important window first and watch whether memory use climbs quickly again.
3. Check Task Manager before you reopen the rest. Press Shift+Esc (Windows or Linux) to see what is using memory before you add more tabs back.
4. Reopen the rest in smaller batches. If you had dozens of tabs open, restoring them in groups makes it easier to spot which batch pushes memory too high again.

If the crash keeps happening within minutes of restarting, that’s a signal one specific tab or extension is the real cause rather than the general accumulation. The next section covers exactly how to identify it.

How Do I Find Which Tab Caused the Out-of-Memory Crash?

Open Chrome’s Task Manager to see memory use broken down by tab and extension, which is the fastest way to catch a repeat offender before it crashes Chrome again. It’s a Chrome-specific tool, separate from whatever task manager your operating system provides, and it shows detail neither one gives you alone.

1. Open Task Manager. Press Shift+Esc on Windows or Linux. On Mac, open the Chrome menu, then More Tools, then Task Manager.
2. Sort by memory. Click the Memory column header so the heaviest tabs and extensions rise to the top of the list.
3. Watch it over time. Leave the window open while you use Chrome normally; a tab whose memory number keeps climbing without leveling off is a strong candidate for a memory leak.
4. Close or reload the worst offender. A single reload sometimes resolves a tab that has been open for days and slowly accumulated memory.

For a deeper look at a specific tab, Chrome also has an internal page at chrome://discards, which lists open tabs with an Urgent Discard button you can use to manually free a tab’s memory and confirm the page reloads cleanly afterward. It’s more of a diagnostic tool than a daily setting, but it’s useful for confirming a suspicion before you decide a tab is the real culprit. Our Chrome Task Manager guide goes through this process in more depth if you want the full walkthrough.

How Do I Turn On Memory Saver to Prevent This From Happening Again?

Turn on Memory Saver in Chrome Settings, then Performance, where it deactivates tabs you’re not actively using so they stop competing for memory with the tabs you are. Reopening a deactivated tab reloads it automatically, so nothing is lost, it’s simply freed up while idle.

Memory Saver has three levels: Moderate keeps tabs active longer before deactivating them and saves the least memory, Balanced is Google’s recommended default, and Maximum deactivates tabs fastest and frees the most memory. If out-of-memory crashes are a recurring problem for you rather than a one-off, Maximum is worth trying even though it means slightly more reload delay when you switch back to an old tab.

The same Performance page has a separate Energy Saver toggle aimed at CPU and battery use rather than memory directly. It stops eligible CPU-intensive background tabs, exempting anything playing audio or in a video call, so it will not interrupt a call in the background. Turning both settings on is reasonable; they solve related but different problems, and neither one costs you anything to leave on. For the fuller picture of how Memory Saver behaves and where its limits are, see our Chrome Memory Saver guide.

Does Closing Tabs or Restarting Chrome Fix It for Good?

Restarting fixes the immediate crash, but it does not fix the underlying pattern if you reopen the same heavy combination of tabs right afterward. Closing tabs helps more directly, since it permanently frees the memory those tabs were holding, but it only works if you’re closing tabs you don’t need anymore.

This is where it helps to be deliberate rather than reactive. Reopening a tab you closed accidentally with Ctrl+Shift+T (Cmd+Shift+T on Mac) reloads the whole page from scratch, including any unsaved form data, which is a real cost if you closed something important in the rush to free up memory. Chrome also supports multi-select for closing a batch at once: Ctrl+click each tab, or click the first and Shift+click the last for a range, then right-click for bulk actions. That’s faster than closing tabs one at a time when you’re trying to bring a crowded window back under control.

Tab groups make this cleanup easier to do without losing track of what’s what. Right-click a tab, choose Add tab to group, name it, and give it a color; a whole finished project’s worth of tabs can then be closed together with confidence, since the group makes clear what belongs together. If tab overload is a recurring issue beyond just the memory crashes, our guide on too many tabs covers the wider set of habits worth changing.

Closing under pressure is risky. The moment right after a crash, when you’re trying to get memory back down fast, is exactly when you’re most likely to close something you needed. If you’re not certain a tab is safe to close, save it first rather than trusting you’ll remember the URL later.

Should I Add More RAM or Switch Browsers?

More RAM helps by raising the ceiling before you hit it, but it does not change how Chrome allocates memory per tab, so extreme tab habits can still cause crashes even on a well-equipped machine. It’s worth doing if your machine is genuinely constrained, but it is not a fix for a single tab with a memory leak or a bloated extension list.

Switching browsers is a bigger decision and rarely solves the underlying issue on its own, since every Chromium-based browser (Edge, Brave, Opera, Vivaldi, Arc) uses the same multi-process architecture Chrome does. What differs between them is the built-in tooling for managing that memory use. Edge, for instance, has its own version of tab deactivation called Sleeping Tabs, which Microsoft’s Edge engineering blog states typically reduces memory usage by 32 percent on average, with a sleeping tab using 37 percent less CPU on average than an active one, according to a 2020 post from that blog. That’s a genuinely useful feature if you’re already considering Edge for other reasons.

If you’re weighing this decision more broadly, our Chrome vs Edge comparison and Edge browser overview go further into the tradeoffs beyond just memory behavior.

Are Extensions Making Chrome Run Out of Memory?

Yes, every enabled extension runs its own background process, and a large or poorly maintained collection adds up the same way a large collection of tabs does. This is one of the most overlooked contributors to repeated out-of-memory crashes, because extensions sit quietly in the background and rarely get a second look once installed.

An extension doesn’t need to be doing anything visible to use memory. Many run continuously to watch for page changes, sync data, or check for updates, and a handful of active extensions can rival the memory footprint of several open tabs. The fix is a periodic audit rather than a one-time cleanup, since new extensions get installed for single tasks and then forgotten.

Open chrome://extensions and look honestly at what’s installed versus what you use regularly. Disabling is reversible and doesn’t delete anything the extension stored, so there’s little risk in being aggressive here. If you use Task Manager and sort by memory, extensions show up in the same list as tabs, sometimes under their own name and sometimes just labeled “Extension,” which is often the fastest way to catch one behaving badly without digging through the full extensions page. Our guide on managing Chrome extensions covers the broader workflow for keeping this list under control long term.

How Do I Get My Tabs Back After an Out-of-Memory Crash?

Check Chrome’s Continue where you left off setting first, since that’s the browser’s own built-in recovery path and reopens the pages you had open when Chrome closed. Find it in Settings, then On startup; if it’s set to Open a specific page or New tab instead, your last session won’t come back automatically after a crash.

That native option has real limits, though. It depends on Chrome recording your last session cleanly, which is not guaranteed during a hard out-of-memory crash, especially if the operating system itself had to force-close Chrome rather than letting it shut down normally. For a single accidentally closed tab, rather than a full crash, Ctrl+Shift+T reopens it, and Chrome’s History menu also lists recently closed tabs and windows if you need to go back further. Our Chrome crashed guide walks through the full set of Chrome’s own recovery options in more detail if you want the complete picture.

Where Chrome’s own recovery falls short is exactly where a dedicated tool picks up. BelayTab’s Recovery screen brings snapshots, deleted sessions, your browser’s recently closed windows, and past exports into one place, so you’re not piecing your session back together from memory after a crash has already scattered it.

How Do I Stop Losing Tabs to Out-of-Memory Crashes for Good?

Stop losing tabs by separating the fix for the crash itself from the fix for protecting what was open when it happened, since Task Manager and Memory Saver address the first problem and a session manager addresses the second. Treating them as one problem is why people still lose work even after doing everything right on the memory-reduction side.

BelayTab exists specifically for the second half of that problem. It’s a free browser extension, no account required, that saves your open windows as named sessions with one click or the shortcut Ctrl+Shift+S, keeping tab groups, pinned tabs, and tab order intact. Because it also snapshots every open window automatically, every five minutes and whenever a window closes, you’re covered even if a crash hits before you had a chance to save anything yourself.

Every saved session also keeps its last 20 versions, so restoring never overwrites what’s currently there, it simply adds another version to the history. That matters if you’ve saved multiple times across a chaotic afternoon and need to go back to an earlier point rather than the most recent one. You can see the full mechanics on our automatic snapshots and restore tabs pages.

Chrome’s out-of-memory crash is frustrating, but it’s rarely mysterious once you know where to look: Task Manager tells you what’s using the memory, Memory Saver and an extension audit cut down how often you hit the ceiling, and a saved session or automatic snapshot makes sure that even when a crash does happen, it costs you a few minutes rather than an afternoon of work.