Google Chrome Crashing: 8 Fixes for "Aw, Snap!" Errors, Freezing & High Memory

Last updated: December 10, 2025

By Sufyan Khan — Founder, FixThatApp  |  Editorial standards

Chrome crashes come in several distinct forms: the "Aw, Snap!" error on specific pages, Chrome freezing and becoming unresponsive, the entire browser crashing on launch, or Chrome quietly consuming all your system memory until Windows or macOS kills it. Each pattern points to a different cause. This guide covers all of them with specific, actionable fixes.

Fix 1: Identify and Kill Memory-Heavy Tabs with Chrome Task Manager

Chrome runs each tab as a separate process — great for stability (one bad tab won't crash everything), but it can consume enormous amounts of RAM when you have many tabs open. Chrome has its own Task Manager to show exactly what's using memory.

1. Press Shift+Esc (Windows) or go to the three-dot menu > More tools > Task Manager.
2. Sort by "Memory footprint" by clicking the column header.
3. Identify any tabs using 500MB+ of memory — these are your likely culprits.
4. Select a problematic process and click End Process.

Also check for extensions using excessive memory. Extensions appear in the Task Manager list too — any extension using more than 100MB is behaving abnormally.

Fix 2: Enable Chrome Memory Saver

Chrome has a built-in feature that automatically puts inactive tabs to sleep, dramatically reducing memory usage. If you keep many tabs open and experience slowness or "Aw, Snap!" errors, this is the single best setting to enable.

1. Click the three-dot menu in the top-right corner > Settings.
2. Click Performance in the left sidebar.
3. Toggle on Memory Saver.

With Memory Saver on, tabs you haven't looked at in a while are put to sleep — they'll reload when you click on them. You'll notice a small leaf icon on sleeping tabs. You can exclude specific sites (like Gmail or Google Docs) from sleeping in the same settings panel.

Fix 3: Disable Extensions to Find the Culprit

Extensions are the #1 cause of Chrome startup crashes and "Aw, Snap!" errors on certain sites. An extension conflict, outdated extension, or extension with malware can destabilize Chrome entirely.

1. Open an Incognito window (Ctrl+Shift+N). Extensions are disabled in Incognito by default.
2. Try to reproduce the crash in Incognito. If Chrome works fine in Incognito, an extension is the cause.
3. Open chrome://extensions in a regular window.
4. Disable all extensions by toggling each off.
5. Re-enable them one at a time, testing Chrome after each one, until the crash returns — that's your problem extension.

Common offenders include ad blockers, VPN extensions, coupon finders, and old extensions that haven't been updated in years.

Fix 4: Clear Cache and Corrupted Site Data

A corrupted cached resource or cookie can cause Chrome to crash or loop on a specific site. Clearing the cache fixes it.

1. Press Ctrl+Shift+Delete (Cmd+Shift+Delete on Mac).
2. Set the time range to All time.
3. Check Cached images and files and Cookies and other site data.
4. Click Clear data and restart Chrome.

If Chrome crashes on only one specific site, you can clear just that site's data: go to chrome://settings/siteData, search for the domain, and delete only that entry without clearing everything.

Fix 5: Disable Hardware Acceleration

Hardware acceleration uses your GPU to speed up rendering. On most systems this works well, but on some GPU/driver combinations it causes crashes — especially on sites with video, animations, or WebGL.

1. Click the three-dot menu > Settings.
2. Click System in the left sidebar.
3. Toggle off "Use hardware acceleration when available".
4. Click the Relaunch button that appears.

If this fixes your crashes, the root cause is likely a GPU driver issue. Visit your GPU manufacturer's website (NVIDIA, AMD, or Intel) and download the latest drivers for your graphics card.

Fix 6: Update Chrome

Running an outdated version of Chrome leaves you exposed to known crashes and security bugs. Chrome usually updates itself, but sometimes the update stalls — especially if Chrome was never fully closed.

1. Click the three-dot menu > Help > About Google Chrome.
2. Chrome will immediately check for updates and display the current version.
3. If an update is available, it will download and apply automatically. Click Relaunch when prompted.

If Chrome is stuck on an old version and won't update, the Chrome installation may be corrupted — skip to Fix 8 (reinstall).

Fix 7: Reset Chrome Settings

If Chrome started crashing after you changed settings, or after malware potentially altered its configuration, resetting to defaults often fixes it. This won't delete your bookmarks, passwords, or saved payment methods.

1. Go to chrome://settings/reset (or Settings > Reset settings).
2. Click "Restore settings to their original defaults".
3. Read the warning — it will reset your startup page, new tab page, search engine, and disable extensions.
4. Click Reset settings.

Fix 8: Uninstall and Reinstall Chrome

If nothing else works, a full reinstall is the cleanest fix. The key is to properly remove the old installation including its profile data, not just install over the top of it.

1. On Windows: Go to Settings > Apps > Installed apps, find Google Chrome, and uninstall it. Then manually delete the C:\Users\[YourName]\AppData\Local\Google\Chrome folder if it still exists.
2. On Mac: Drag Chrome from Applications to Trash, then delete ~/Library/Application Support/Google/Chrome.
3. Download a fresh installer from google.com/chrome and install.

When you log in to your Google account in the fresh Chrome, your bookmarks and passwords will sync back automatically.

What NOT to Do

Frequently Asked Questions