Stabilize Chrome extensions, profile, cache, and hardware acceleration

When to use this guide

Use this guide when Chrome shows Aw, Snap!, crashes while loading a page, works differently from another browser, or appears affected by extensions, profile data, cache, hardware acceleration, or device resources.

Before you start

Do not clear all browser data as the first move if the issue affects only one site. Start with isolation so you can tell whether the problem is Chrome, the network, DNS, or the server. Save any form work before reloading or clearing site data.

Step 1: Test Incognito

Open the page in an Incognito window. Expected result: if the page works, the issue is likely extension, cookie, cache, or profile data. If it still crashes in Incognito, continue to profile and device checks.

Step 2: Disable extensions in batches

Disable extensions, reload the page, then re-enable them one at a time. Expected result: the page stops crashing when the conflicting extension is disabled. If a workplace policy manages extensions, involve IT rather than removing required security tools.

Step 3: Try a temporary Chrome profile

Create a new Chrome profile without signing in or syncing extensions. Expected result: if the new profile works, the old profile has corrupted settings, cache, cookies, or extension state. Move bookmarks and essentials carefully; do not immediately sync every old extension back into the new profile.

Step 4: Clear site data only for the affected site

Clear cookies and cached files for the affected site first. Expected result: stale or corrupt site data is removed without wiping unrelated sessions. If login state matters, make sure you have credentials or recovery access before clearing cookies.

Step 5: Toggle hardware acceleration

Turn hardware acceleration off, restart Chrome, and retest. Expected result: GPU or driver-related crashes stop. If performance worsens or the problem is unrelated, restore the setting after testing.

Step 6: Check device and network clues

Restart the device, close heavy tabs, update Chrome, and test another network. If Chrome shows DNS_PROBE_FINISHED_NXDOMAIN, use the DNS error guide. If the page returns 500 or 502 in every browser, move to HTTP error troubleshooting.

Expected outputs

If the problem returns

Review what re-enabled just before the crash returned: an extension, synced setting, restored profile, security tool, or hardware acceleration. If sync reintroduces the problem, create a clean profile and sync only bookmarks/passwords first, then add extensions one at a time.

Verify

Verify by loading the original URL in the original profile, Incognito, and another browser. The fix is solid when the page loads repeatedly without Aw, Snap! and no new DNS or HTTP error appears.

Rollback or escalate

Re-enable extensions one at a time, restore hardware acceleration if it did not help, and avoid deleting a profile until bookmarks and passwords are safe. Escalate to device or workplace IT if every page crashes, security software is involved, or Chrome is managed by policy.