Chrome Crashes on Video Pages? Fix RAM vs Extension Causes

By

Updated

Chrome crashing on video-heavy pages, going white or showing “Aw, Snap!”, usually comes down to one of two things: your computer running out of memory to keep the video playing, or an extension interfering with the page’s video player. The fastest way to tell them apart is to open the same page in an Incognito window. If it plays fine there, an extension is the cause. If it still crashes, memory or graphics handling is more likely, and the fix depends on which branch you’re in.

Before you start

Applies to: Google Chrome. Not version-specific. No account sign-in is required. You’ll use Chrome’s built-in Task Manager and the extensions page, both reachable without any special permissions.

Why Chrome crashes on video-heavy pages

Every open tab in Chrome runs largely in its own process, and video decoding is one of the most memory- and CPU-intensive jobs a tab can do. When a video-heavy page pushes that process past what your system can spare, Chrome or the operating system kills it rather than let the whole browser lock up, and you get the white “Aw, Snap!” page. One Google Chrome Community thread described exactly this trigger: a tab kept crashing and going white specifically when a video was playing and several other tabs were open at the same time. A separate Google Chrome Community thread reported the same pattern with no extension involved: the browser crashing specifically when watching videos, which points to the same underlying resource pressure rather than a single buggy site.

But video pages crash for more than one reason, and the fix only works if it matches the actual cause. There are three branches, each with its own signal:

  • Memory (RAM) exhaustion. Signal: the crash gets worse the longer you’ve had tabs open, or the more tabs you have running at once, and it happens on more than one video site.
  • An extension conflict. Signal: the crash happens even with just one video tab open, often quickly after the page loads, and it goes away in an Incognito window (where extensions are off by default).
  • A single site’s video player. Signal: only one specific site crashes, other video-heavy sites play fine, and the crash happens in Incognito too.

How to fix Chrome crashing on video pages

If it’s memory exhaustion

Check what’s actually using your memory before you start closing things at random.

  1. Open Chrome’s built-in Task Manager (separate from your operating system’s task manager). On Windows, Linux, and ChromeOS, press Shift+Esc. On a Mac, there’s no default shortcut; open it from the Window menu in the menu bar, then choose Task Manager.
  2. Sort by the Memory Footprint column and look for tabs using an unusually large amount, especially other video or streaming tabs sitting in the background.
  3. Select the heaviest tab you’re not actively using and click End process at the bottom of the Task Manager window to free its memory.
  4. Reload the video page and let it play alone for a minute before reopening other tabs, to confirm memory was really the limit.
  5. If it keeps happening even with few tabs open, your device may simply not have enough RAM for high-resolution video plus everything else running, in which case lowering the video’s playback quality is the more durable fix than closing tabs each time.

If it’s an extension conflict

Confirm the extension theory first, then find the specific extension.

  1. Open an Incognito window (Ctrl+Shift+N on Windows and ChromeOS, Cmd+Shift+N on Mac) and load the same video page.
  2. If the video plays without crashing, go to chrome://extensions in a regular window.
  3. Turn off every extension using the toggle next to each one.
  4. Reload the video page to confirm it now plays normally.
  5. Turn extensions back on one at a time, reloading the video page after each, until the crash comes back. The last one you enabled is the cause; remove or update it.

Ad blockers, video downloaders, and script-injecting extensions are the most common culprits here, since they actively rewrite or intercept the page’s video player instead of just sitting passively in the toolbar.

If it’s one specific site

When only one site crashes and the same crash happens in Incognito, the problem is more likely that site’s player code or your GPU driver reacting badly to it, not something you can fix inside your Chrome settings alone.

  1. Go to chrome://settings/system.
  2. Turn off Use graphics acceleration when available, then relaunch Chrome using the button that appears.
  3. Reload the site that was crashing. If it now plays, your GPU driver is struggling with that site’s video decoding, and updating your graphics driver through your operating system is the longer-term fix.
  4. If turning off graphics acceleration doesn’t help either, the site’s own player is the likely cause, and reporting the crash to the site (with the exact page and what you were doing) is the only path left, since it isn’t something Chrome settings can work around.

What does not fix this

People chasing this crash tend to try the same handful of things before finding the branch that actually applies to them.

  • Reinstalling Chrome. This resets Chrome’s own files, but it doesn’t add RAM to your device or remove a problematic extension, both of which live outside the installer.
  • Clearing cache and cookies alone. Cached files rarely cause a tab to run out of memory mid-playback, so clearing them usually leaves the crash exactly as it was.
  • Repeatedly reloading the tab. If the cause is memory pressure from other open tabs, reloading just restarts the same process under the same constraint, so it tends to crash again at roughly the same point.
  • Switching to Incognito as a permanent fix. Incognito is useful for diagnosing an extension conflict, but it is not a solution to keep using day to day. Incognito windows still consume significant memory of their own, so if your real problem is a low-RAM device, Incognito can end up just as crash-prone once you have a few tabs open.

Frequently asked questions

Why does Chrome only crash when a video is playing and I have multiple tabs open?

Video decoding is one of the heaviest jobs a browser tab does, and each open tab already holds its own share of memory. When several tabs are open at once, and one of them starts decoding video, the combined memory demand can exceed what your system can give that process, and Chrome kills the tab rather than let the whole browser become unresponsive.

Does Incognito mode actually fix video crashes in Chrome?

It fixes crashes caused by an extension, since extensions are disabled by default in Incognito. It does not fix crashes caused by memory exhaustion or a site’s own player, since Incognito windows use real memory too and don’t change how a site’s video code behaves.

Can hardware acceleration cause Chrome to crash on video sites?

Yes, in some cases. Graphics acceleration hands video decoding off to your GPU, which is normally faster, but if the GPU driver mishandles a particular site’s video format, the tab can crash instead of just playing slowly. Turning acceleration off in chrome://settings/system is a quick way to test whether this is the cause.

Chrome crashing on video pages almost always traces back to memory pressure, a conflicting extension, or a specific site’s player, not a broken browser install. Match the fix to the branch that fits your symptoms rather than working through every fix at once, and the crash usually stops for good.

Related reading


Discover more from Chrome Story

Subscribe to get the latest posts sent to your email.

About the author

How we report · Send a correction