日本語
STEP-BY-STEP GUIDE

Isolate Chrome “Aw, Snap! / Out of Memory” errors by testing load and extensions

Troubleshooting guideSources checked: 2026-09-054 stepsFaultNote editorial team

What to do first

Close all but the affected tab to free memory, then narrow the cause through Incognito, extensions, and updates.

This is a general troubleshooting guide, not an announcement of a current outage.

Affected products and symptoms

Product
Google Chrome for computer
Versions and conditions
Chrome for Windows/macOS (general procedure)
Error codes and identifiers
Aw, Snap!Out of Memory

Symptoms

  • A page crashes because memory is exhausted, or a tab cannot load

Causes and conditions

Many tabs, apps, downloads, or extensions may consume enough memory to prevent the page from loading.

Before you start

  • Save data entered in forms and important tabs
  • Check Chrome Sync
  • Record whether the same page opens in another browser

Precautions

  • Deleting cache and cookies may sign you out of sites
  • An Out of Memory message alone does not establish faulty RAM

Tools and official pages used in this guide

Google Chrome for computer troubleshooting sequence: Free memory; Compare in Incognito; Review extensions; Update Chrome
Procedure overview created by FaultNote. Read the precautions and full instructions before changing settings. Read the full steps

Step-by-step instructions

  1. 01

    Free memory

    #

    Close every tab except the failing one, stop other apps and downloads, and reload.

    Use the three-dot menu at the upper right to open the stated pages. Reproduce with the same URL, Chrome profile, zoom level, and video position. Keep the effect of closing tabs and apps separate from the effect of changing settings.

  2. 02

    Compare in Incognito

    #

    Open Menu > New Incognito window and load the same URL. If it opens, consider cache or extensions.

    Improvement in Incognito points to an extension or stored data. Because deleting cookies signs you out, limit deletion to the affected site and confirm that you can sign in again first.

  3. 03

    Review extensions

    #

    Open Menu > Extensions > Manage extensions, remove unnecessary extensions, then disable the remaining ones one at a time and test.

    Use the switches on Manage extensions rather than editing chrome://extensions directly. Test one at a time, restore unrelated items, and record each name and result.

  4. 04

    Update Chrome

    #

    Open the three-dot menu > Help > About Google Chrome and wait for the automatic check. If an update is downloaded, select Relaunch. Confirm Chrome is up to date at chrome://settings/help, then open only the original tab and retest.

    After changing the GPU switch under Settings > System, select Relaunch. Restore the switch if the same page does not improve; if it does, install an official GPU-driver update and retest with acceleration enabled.

    Completion criteria: the same page opens after reducing load, and reproduction differs before and after disabling a particular extension. If unmet, do not repeat the same operation; follow the next branch: restart the PC and compare the effect of background apps.

    Official links for this step

    Check before continuing

    Decision: open the three-dot menu > Help > About Google Chrome, wait for the update check, relaunch if updated, confirm Chrome is up to date at chrome://settings/help, and retest only the original tab. If changing the GPU switch, relaunch and restore it when ineffective.

Check the result

  • The same page opens after reducing load
  • Reproduction differs before and after disabling a particular extension

If the problem continues

  • Restart the PC and compare the effect of background apps
  • If another browser also fails, investigate the site or network

Scope of this guide

Troubleshooting guide — Google's official page-crash diagnostic procedure; it does not by itself establish hardware failure.

Frequently asked questions

Should I delete all browsing data first?

First compare in an Incognito window. If needed, target only cookies and cache afterward.

Official sources and dates

Source publication or resolution date: Not specified. Sources checked: 2026-09-05. The check date is not the date the problem first occurred. Interface labels can vary between versions and display languages.

Related troubleshooting guides

← Search English guides