Chrome Aw, snap page crash

The "Aw, snap" page in Chrome reports that a tab's renderer process crashed, and that the site or the browser cannot keep that tab alive. It is a process-level failure, not a plain page error: the renderer that draws the page was killed by the OS or the browser. On the same screen Chrome offers "Reload", and for a single-tab loss that often recovers the page. When it recurs, the crash has a root cause worth finding.

What Aw snap means

Chrome runs each tab's drawing in a separate renderer process. When that process dies, the tab cannot repaint and Chrome shows the crash warning instead of the content. The message appears because:

• the renderer hit a genuine access violation in the page's code,
• the browser's memory or GPU layer terminated it, or
• an extension killed the tab's process.

It is distinct from a network time out or a DNS failure; the connection may be fine and the server fast, yet the tab still dies client-side.

Read the fault first

Do not reload blindly and lose the diagnosis. The clues to a repeated crash live in three places:

1. Which tab and action: does it crash after the same interaction (video, a large list, a file), on every visit, or only on one device?
2. Other tabs: if several tabs crash together, pull the browser-level pressure or the GPU path rather than the site.
3. Chrome diagnostics: chrome://crashes gives recent crash metadata without a manual flood of logs.

Fix at each layer

Browser resources

Renderer processes are terminated when Chrome runs out of memory or the OS reclaims it:

1. Close heavy tabs and check Chrome's memory use in chrome://memory-internals or the Task Manager (Shift+Esc in Chrome).
2. Reload the crashing page once the pressure is gone. A page that crashed because the browser was starved loads fine afterwards.
3. Disable background extensions that consume memory and test for a while to see if a specific add-on triggers the crash.

Extensions are common culprits because they can run in the same rendering path. Turn off extensions one by one (or open a fresh profile with only the essential ones) and reproduce the crash.

Graphics and acceleration

GPU composition is a frequent crash source. If chrome://gpu reports an issue with hardware acceleration:

1. Try disabling hardware acceleration in Settings > System and reload.
2. If the crash disappears, update your graphics driver or Chrome; an outdated driver is often the cause.
3. Re-enable acceleration later and confirm the site no longer crashes, so you do not carry a permanent workaround.

Site code

When a specific page crashes reliably on the same trigger, the page's JavaScript or resources are suspect:

1. Open the page in a fresh, extension-free profile, or use an incognito window as a quick clean test.
2. Use Chrome DevTools and watch for an unhandled exception or an out-of-memory allocation in the console and Performance panel.
3. Reduce heavy JavaScript and large canvas or WebGL work; a page that grows an unbounded list or allocates constantly can push its renderer over the limit. See heavy JavaScript for the general shape.

Prevention

• Keep Chrome current; each release fixes renderer and GPU crash classes.
• Remove or update extensions you do not need, and reproduce suspected site crashes in a clean profile.
• On the site side, fix unbounded loops, huge canvas buffers and runaway allocations, and avoid drawing work that spikes memory at one time.

A single Aw, snap after a browser update or a memory spike is usually incidental, so reload and move on. Repeatable crashes on the same page are a bug in the page's code or in a browser layer, and the fixes above isolate which one. For the surrounding network symptoms, start from the site not loading guide, and for a partial page where assets abort mid-load, see ERR_ABORTED.