sbox_fatal_memory_exceeded is a Google Chrome crash code that appears when one tab, extension, or plugin process asks for more memory than Chrome’s security sandbox will hand out. Chrome kills that single process instead of letting it drag down the whole computer, so you see an Aw, Snap! page. The fastest fix is to close the heavy tab, restart Chrome, and turn off the extension that is eating memory.
What does sbox_fatal_memory_exceeded mean?
The sandbox is the walled-off space Chrome runs each tab and extension in, and it has a hard ceiling on how much memory any one process may claim. When a process pushes past that ceiling, Chrome shuts it down on purpose and reports the code sbox_fatal_memory_exceeded. It is a protective stop, not a sign that Chrome is broken or that your machine is infected.
Two things follow from that. First, the crash is usually about one specific thing you had open, not about Chrome as a whole. Second, a fix that lowers memory pressure will work, and a fix that only clears settings usually will not.
What causes the error?
- A memory-hungry page. Web apps, map views, long chat threads, and browser games can climb steadily until the process hits the ceiling.
- A leaking extension. An extension that never releases memory will take a tab down with it, and it often does so on the same site every time.
- Too many open tabs. Each tab has its own process, so a crowded window leaves very little headroom for any one of them.
- A system that is low on free RAM. If other apps have already claimed most of the memory, Chrome hits the wall much sooner.
- Malware or an unwanted program quietly consuming resources in the background.
Before you start
- Applies to: Google Chrome and other Chromium browsers, including Microsoft Edge, on Windows, macOS, Linux, and ChromeOS.
- You need: no special account or admin rights for the main fixes.
- Time: about five minutes for the first four steps.
- Note the page you were on when the crash happened. That single detail solves most cases.
How do I fix sbox_fatal_memory_exceeded?
Work down the list in order. Stop as soon as the crash stops coming back.
1. Close the tab and restart Chrome
- Close the tab that crashed, along with any other tabs you do not need right now.
- Close every Chrome window.
- Open Chrome again and load only the page you were using.
This clears the process that was stuck and gives the page a fresh start. If the crash returns on the same site within a minute or two, that site is the cause and the next steps matter more than this one.
2. Find the process eating your memory
Chrome has its own Task Manager, and it is the single most useful tool here because it names the exact tab or extension at fault.
- Open the three-dot menu, then go to More tools and Task manager. You can also press Shift + Esc on Windows, Linux, and ChromeOS, or use Search + Esc on a Chromebook.
- Click the Memory footprint column heading to sort the list from largest to smallest.
- Watch the top entry for a few seconds. A number that keeps climbing and never falls back is a leak.
- Select that row and click End process.
Whatever sits at the top of that list is your culprit. If it is an extension, go to the next step. If it is a tab, keep that site to one window and reload it less often.
3. Turn off extensions and add them back one at a time
- Type chrome://extensions in the address bar and press Enter.
- Switch every extension off.
- Use Chrome normally for a while. If the crash is gone, switch extensions back on one at a time, giving each one a day of ordinary use.
- Remove the extension that brings the crash back.
Ad blockers, shopping helpers, video downloaders, and anything that rewrites pages as they load are the usual offenders, because they hold a copy of the page in memory.
4. Let Chrome put idle tabs to sleep
Chrome can free the memory held by tabs you have not touched in a while, which leaves far more headroom for the tab you are actually using.
- Open Settings and choose Performance.
- Turn on Memory Saver.
- Add any site that must stay live, such as a music player or a dashboard, to the Always keep these sites active list.
5. Update Chrome and your operating system
- Open the three-dot menu, then Help and About Google Chrome.
- Let the update download, then click Relaunch.
- Install any pending system updates and restart the computer.
Memory handling in Chrome changes often, and a stale build can crash on pages that a current one handles without complaint.
6. Turn off hardware acceleration
On machines that share memory between the graphics chip and the system, hardware acceleration can push a tab over the ceiling on video-heavy pages.
- Open Settings, then System.
- Switch off Use graphics acceleration when available.
- Click Relaunch.
If this fixes the crash but pages feel slower, turn it back on and update your graphics driver instead.
7. Scan for malware, then reset Chrome
Warning: resetting Chrome switches off every extension and clears your cookies, site settings, and pinned tabs. Bookmarks, history, and saved passwords stay, but you will have to sign in to sites again. Treat this as a last resort.
- Run a full scan with your antivirus program and remove anything it flags.
- Open Settings, then Reset settings.
- Choose Restore settings to their original defaults and confirm with Reset settings.
How do I stop it from happening again?
- Keep heavy web apps in their own window rather than buried among thirty tabs.
- Leave Memory Saver on.
- Review your extensions every few months and remove the ones you no longer use.
- Close other large applications before a long session in a browser-based tool.
- If your computer has 4 GB of RAM or less, expect this ceiling to be reached sooner and plan your tab habits around it.
Frequently asked questions
Does sbox_fatal_memory_exceeded mean I have a virus?
No. The code means a Chrome process hit its sandbox memory limit and was shut down on purpose. Malware can push memory use high enough to trigger it, so a scan is worth running, but the error itself is a safety mechanism rather than an infection.
Why do I get this error in Microsoft Edge?
Edge is built on Chromium, the same engine Chrome uses, so it inherits the same sandbox and the same crash codes. Every fix on this page works in Edge. The settings live in the same places, under Settings and then System and performance.
Will adding more RAM fix it?
More RAM helps when the whole system is starved for memory, and it will reduce how often the error shows up. It will not help if a single leaking extension is the cause, because that process will climb until it hits the sandbox ceiling no matter how much memory the machine has.
Will I lose my open tabs?
Only the crashed tab closes, and Chrome usually offers to restore it. If it does not, press Ctrl + Shift + T on Windows, Linux, and ChromeOS, or Command + Shift + T on a Mac, to reopen the last tab you lost.
Wrapping up
sbox_fatal_memory_exceeded is Chrome protecting your computer from one greedy process, so the fix is to find that process rather than to rebuild the browser. Chrome’s own Task Manager names the offender in seconds, and turning on Memory Saver keeps the problem from returning. If the crash follows you across profiles and devices on the same site, the site itself is the problem and there is nothing to fix on your end.
