If Chrome keeps crashing with an out-of-memory message, the cause may be one demanding tab, an extension, or a shortage of memory across your whole computer—not necessarily a broken browser. These ten checks start with quick ways to identify the problem, then cover Chrome settings, system resources, and profile troubleshooting. They’re for anyone using Chrome on Windows, macOS, Linux, or a Chromebook who wants to narrow down the cause without immediately reinstalling the browser.
1. Find the tab or process using Chrome’s Task Manager
Chrome has its own Task Manager, which shows memory use for individual tabs, extensions, and browser processes rather than only reporting Chrome as one item in your operating system’s process list. On Windows, Linux, and ChromeOS, press Shift+Esc; on macOS, open the Window menu and choose Task Manager. Sort by the Memory footprint column, note any unusually demanding tab or extension, and end only the process you recognize as problematic, since ending a tab can discard unsaved work and ending a browser process may close related activity.
2. Close high-memory tabs and reduce the number kept open
Every active tab can use memory for its page, scripts, images, video, and embedded tools, so a group of complex tabs can exhaust available RAM even when each one seems manageable. Save forms or documents first, then close tabs you do not need, especially dashboards, web-based design tools, long-running video streams, and pages with large interactive maps. If you need to keep a page for later, bookmark it or use a reading list rather than leaving dozens of resource-heavy pages running in the background.
3. Turn on Chrome’s Memory Saver
Memory Saver deactivates eligible inactive tabs so Chrome can make their memory available to active tabs and other applications; returning to a deactivated tab reloads it. Open Chrome’s three-dot menu, go to Settings, then Performance, and turn on Memory Saver, choosing an available mode if Chrome presents the options. Add sites that must stay active—such as a web app playing audio or a page with work in progress—to the always-active list, because a tab that reloads may lose temporary state that was not saved to the site.
4. Disable extensions to identify a faulty one
Extensions run alongside pages and can consume memory or interact badly with particular sites, so disabling them is a useful test when crashes began after installing or updating one. Visit chrome://extensions, switch off all extensions, and use Chrome long enough to see whether the crashes stop; if they do, turn extensions back on one at a time until the problem returns. That process identifies a likely cause more reliably than removing everything at once, and it lets you check whether an extension has an update or a documented setting that reduces its activity.
5. Update Chrome and restart it
An outdated browser can retain bugs that have been corrected in a later release, so check for an update before making more disruptive changes. Open the three-dot menu and choose Help, then About Google Chrome; Chrome checks for updates on that page and may ask you to relaunch to finish installing one. Save your work before relaunching, and restart the computer as well if Chrome remains unstable, since a full restart closes background applications and clears processes that may have been consuming memory for a long time.
6. Check whether the whole computer is short on memory
Chrome may be the application displaying the error while another program is using much of the computer’s memory, so check system-wide usage during a crash or just before one. Windows users can look at the Memory section in Task Manager, macOS users can inspect Memory and Memory Pressure in Activity Monitor, and Linux users can use their desktop’s system monitor. Close programs you do not need, such as multiple video editors or virtual machines, and remember that operating systems use disk space for paging or swap when RAM is tight; very little free storage can make that fallback less effective.
7. Test whether one particular website triggers the crash
If the error repeatedly appears on the same site, the page may be unusually demanding, have a script that keeps growing in memory, or be handling a large file. Open a different site and watch whether Chrome stays stable, then try the problem page in a new tab after saving any work; you can also compare it in a Guest window to rule out some profile-specific settings and extensions. For a large PDF, spreadsheet, or design project, close other tabs first and use the site’s save or export feature regularly, because a page crash can still lose unsaved changes.
8. Try a Guest window or a fresh Chrome profile
A temporary Guest window helps test Chrome without changing your main profile’s bookmarks, settings, or saved data; open the profile menu near the top of the browser and choose Guest if that option is available. If the problem does not occur in Guest, create a separate Chrome profile and test there, then add extensions gradually rather than copying every setting immediately. This can reveal a damaged or misconfigured profile, but do not delete your old profile as a first step: confirm that important bookmarks and other data are synced or backed up before removing anything.
9. Test hardware acceleration if crashes involve graphics
Hardware acceleration lets Chrome use the computer’s graphics hardware for some tasks, and graphics-driver problems can sometimes make the browser unstable, particularly during video playback or graphics-heavy pages. In Settings, open System and change the Use graphics acceleration when available setting, then relaunch Chrome and compare how it behaves. This is a targeted test rather than a universal memory fix: if the out-of-memory crashes continue unchanged, restore the previous setting, since disabling acceleration can shift more work to the processor and may make graphics-intensive pages slower.
10. Free storage and check for broader system problems
Low disk space does not prove that Chrome is out of physical memory, but it can interfere with temporary files and the operating system’s ability to manage memory pressure. Check your operating system’s storage settings, remove files you no longer need, and empty the recycle bin or trash only after checking its contents; avoid deleting Chrome profile folders manually. If other applications also crash or the computer reports memory errors, investigate system updates, background software, or hardware with the computer manufacturer’s guidance, because a browser reinstall will not repair a system-wide fault.
How to Choose
Start with the least disruptive checks: use Chrome Task Manager, close a clearly demanding tab, and check overall system memory. If the crashes happen only on one site, focus on that page and test it without extensions; if they happen across many sites, check extension behavior, Chrome updates, and system-wide resource use. Memory Saver is a good ongoing setting when you keep many tabs open, while a Guest window or fresh profile is more useful for separating browser-profile problems from computer-wide ones.
Match the fix to the evidence instead of changing several settings at once. A sudden change after installing an extension points toward testing that extension; crashes during video or graphics-heavy work make the acceleration test more relevant; and similar failures in other apps suggest looking beyond Chrome. Keep track of what you change and test the browser between steps, so you can identify which change helped and undo any that made things worse. If crashes persist despite these checks, record the exact error, the affected pages, and whether other applications fail too before seeking support.
Frequently Asked Questions
Does an out-of-memory message mean my computer needs more RAM? Not necessarily. A single tab, extension, or browser process can hit a limit or behave badly even when the computer has memory available, so check Chrome’s Task Manager and the operating system’s memory view before deciding that an upgrade is needed.
Why does Chrome crash when I have only a few tabs open? A small number of tabs can still use substantial memory if they contain large files, video, complex web apps, or scripts that keep accumulating resources. Use Chrome’s Task Manager to compare the tabs and extensions rather than judging the load only by tab count.
Will clearing browsing data fix an out-of-memory crash? Usually, clearing cache is not the first or most direct fix for a shortage of available memory. It may help with certain site-loading problems, but it can sign you out of websites or remove stored site data, so try it only when there is a reason to suspect a site-data issue.
Does Memory Saver close tabs or erase their contents? It deactivates eligible inactive tabs to free memory; it does not simply remove them from the tab strip. When you return, Chrome reloads the page, and unsaved or temporary page state may not be preserved, so save work and exempt important sites where appropriate.
Should I reinstall Chrome? Reinstallation is rarely the best first move because the cause may be a particular site, an extension, or low system resources. Try a Guest window and the other checks first; if you do reinstall, confirm that important profile data is synced or backed up and use Google’s official Chrome download source.
Final Thoughts
When Chrome keeps crashing out of memory, first find out whether one tab or extension is responsible, then check whether the entire computer is running short on resources. Memory Saver, a clean profile test, and a focused graphics setting test can help, but they solve different kinds of problems. Change one thing at a time, protect unsaved work, and use recurring crashes across other apps as a sign to investigate the computer rather than Chrome alone.