Fix Chrome Aw Snap with Many Tabs on Windows 11

Chrome shows Aw, Snap! when you open too many tabs on Windows 11. The fix is to increase the browser's memory limit or close memory-hogging extensions. I'll walk you through it.

You're working on a research project, you've got fifteen tabs open—news, docs, a video, your email—and suddenly one tab goes gray with that sad little icon and the words “Aw, Snap!”. It happens again when you try to reopen it. You're on Windows 11, using Chrome version 120 or later, and it's not just one tab—it's the third time this hour. Sound familiar?

What's actually going on?

Chrome runs each tab as its own process, and each process needs a slice of your PC's RAM. When you open too many tabs, Chrome hits a thumb rule called the per-process memory limit. Once it crosses that, the browser kills the tab to keep the whole thing from freezing. On Windows 11, the default limit is often set to 512 MB per tab, which is fine for a few tabs, but with a dozen or more, you're starving them.

The real culprit is usually a combination of heavy tabs (like YouTube or Google Maps) and a few sneaky extensions that eat memory in the background. But the good news is you can raise the limit—if you're careful.

Fix #1: Give Chrome more memory (the nuclear option, but it works)

This tweak is not officially supported, so Chrome might reset it after an update. But for now, it's the most direct fix.

Close Chrome completely. Make sure no Chrome processes are running in the background. Right-click the taskbar and select Task Manager. Look for “Google Chrome” under Apps. If you see any, select them and click End task. You can also check the system tray for a Chrome icon—right-click it and choose Exit.
Open the Chrome shortcut properties. Right-click the Chrome icon on your desktop or taskbar, select Properties.
In the Shortcut tab, find the Target field. It'll look something like:
```
C:\Program Files\Google\Chrome\Application\chrome.exe
```
Add a space, then paste this after the exe path:
```
--max_old_space_size=1024
```
This tells Chrome to allow 1024 MB (1 GB) per tab's JavaScript heap. You can adjust it, but I'd start there. Don't go above 2048 unless you have 16 GB of RAM or more—you'll actually make things slower.
Click Apply and then OK. Now launch Chrome from that shortcut. If you get a warning about an invalid shortcut, double-check that you put the space correctly.

After you apply this, restart Chrome and open a fresh batch of tabs. You should notice that tabs load without crashing. If it still happens, the next step is more likely to help.

Fix #2: Find the memory hog extensions

Extensions are the silent killers. I've seen a simple ad-blocker eat 300 MB. Here's how to see what's going on:

Open Chrome and type chrome://memory-internals in the address bar. Press Enter.
You'll see a list of processes and how much memory each uses. Look for anything with “Extension” in the name. Write down the names and the memory numbers.
Go to chrome://extensions (or click the three-dot menu > More tools > Extensions).
For each extension that's using more than 50 MB, try disabling it by toggling the switch off. You don't have to uninstall it—just turn it off for now.
Restart Chrome (close all windows and reopen) and see if the Aw, Snap! goes away. If it does, you've found the culprit. You can then either keep it off or find a lighter alternative.

Fix #3: Turn on Chrome's built-in memory saver

Chrome has a feature that automatically frees up memory from inactive tabs. It's not perfect, but it's a start.

In Chrome, go to the three-dot menu > Settings.
Scroll down to Performance.
Turn on Memory Saver. You'll see a toggle—switch it on.
Also, underneath that, you can adjust Active tab loading—if you want, set it to “Moderate” or “Aggressive” so Chrome unloads tabs sooner. I recommend “Aggressive” if you're constantly running into this error.

Once you turn this on, Chrome will discard inactive tabs after a certain time. When you switch back, the tab reloads from scratch. That's a trade-off, but it beats the “Aw, Snap!” screen.

What if it still fails?

If you've done all three and you're still getting the error, then you've got a deeper problem. Try these:

Update Chrome—go to chrome://settings/help and let it update. Sometimes it's a bug that's already fixed.
Check your RAM—if you have less than 8 GB, you're fighting a losing battle with many tabs. Close other apps like Slack and Spotify—they sit in the background and eat RAM.
Run a virus scan—I've seen a miner in the background chew up all your memory, causing Chrome to crash on any tab. Windows Defender should be on, but run a full scan.
Reset Chrome settings—go to chrome://settings/reset and click “Restore settings to their original defaults.” This will remove your extensions and clear some caches, but it won't delete your bookmarks or passwords.

If none of that works, I hate to say it, but switch to Chromium Edge or Firefox for a week. They handle memory differently, and you might find they don't crash. But the fixes above should solve it for 90% of you.