How to Fix Chrome Tabs Crashing With the Aw Snap Error

What Causes This?

Chrome’s Aw, Snap! error means the tab process crashed. The most common causes are memory pressure, a bad extension, a problem with the site itself, a corrupted Chrome profile, or GPU rendering issues. Repeated crashes can also come from outdated Chrome, outdated graphics drivers, aggressive security software, or another app using too much CPU or RAM in the background.

Common Symptoms

• A tab suddenly shows the Aw, Snap! message instead of the webpage
• Chrome crashes more often when many tabs are open
• One website fails every time while other sites load normally
• Chrome becomes slow, freezes, or uses unusually high memory
• The problem started after installing an extension, changing a security app, or updating Chrome or a GPU driver

How to Fix It Manually

1. Restart Chrome and your computer

   • Close Chrome fully.
   • On Windows, press Ctrl+Shift+Esc to open Task Manager. End any remaining Google Chrome processes.
   • On macOS, open Activity Monitor and quit any stuck Chrome processes.
   • On Ubuntu or Fedora, use System Monitor and end any leftover Chrome processes if needed.
   • Restart your computer, open Chrome, and test the same page again.

2. Check memory usage and close heavy apps

   • Open your system’s task manager or monitor and sort by Memory.
   • Close apps you do not need, especially games, editors, virtual machines, or other browsers.
   • If Chrome is using a lot of RAM, reduce the number of open tabs and windows.
   • If only one site crashes, the problem may be that page rather than your whole browser.

3. Disable Chrome extensions

   • Open chrome://extensions/
   • Turn off all extensions.
   • Restart Chrome and try the page again.
   • If the crash stops, turn extensions back on one at a time until the problem returns. Remove or replace the one causing it.

4. Clear Chrome cache

   • Press Ctrl+Shift+Delete on Windows or Linux, or Command+Shift+Delete on macOS.
   • Set Time range to All time.
   • Select Cached images and files.
   • Only include Cookies and other site data if the problem affects sign-in or multiple sites.
   • Click Delete data, then restart Chrome.

5. Turn off hardware acceleration

   • Open chrome://settings/system
   • Turn off Use graphics acceleration when available.
   • Click Relaunch.
   • If this fixes the crashes, update your GPU driver from your PC maker, GPU vendor, or through your Linux distribution’s normal update tools before turning it back on.

6. Update Chrome and your system

   • Open chrome://settings/help and let Chrome install any available update.
   • Also install pending system updates on Windows, macOS, Ubuntu, or Fedora, then restart.
   • If the issue started right after an update, test again after a full reboot before changing more settings.

7. Reset Chrome settings

   • Open chrome://settings/reset
   • Click Restore settings to their original defaults.
   • Confirm the reset.
   • This disables extensions and resets startup and search settings, but it does not delete bookmarks.

8. Create a new Chrome profile if the issue keeps happening

   • Click your profile icon in Chrome.
   • Choose Add and create a new profile.
   • Test the same sites in the new profile.
   • If the crashes stop, your original profile is likely damaged.

Fix It Automatically with Kudu

Kudu can help you rule out common system-side causes of Chrome tab crashes. Its Performance Monitor shows which processes are using the most CPU and memory, and its Startup Manager can help you disable unnecessary startup apps that keep eating resources in the background. Kudu’s System Cleaner can also clear supported browser caches for review, while preserving saved passwords, history, and cookies unless you choose separate privacy actions.

Download Kudu Free →