If Aw, Snap! only shows up on YouTube tabs while every other site loads fine, the video decoding path is the most likely trigger, not general memory pressure. If Chrome eventually crashes on any tab you leave open long enough, treat it as a system-wide memory problem instead, and start with the all-tabs fixes below. Check which pattern you actually have before you change any settings.
Who this applies to
Google Chrome. Not version-specific. Reported on Windows, macOS, and Chromebooks, on both signed-in and guest profiles. You do not need any special settings enabled to hit this.
Why this happens
“Aw, Snap!” means Chrome’s renderer process for that tab died. YouTube decodes high-bitrate video using your GPU while running a busy comment and recommendation feed at the same time, which makes it the first tab to fail when something is already close to the edge. That is why the crash can look “YouTube-only” even when the real cause is broader. A few distinct causes produce this same symptom, and each needs a different fix.
- GPU or video-decoder conflict. Signal: the crash happens specifically during playback, often within seconds of a video starting, and other heavy sites (Google Docs, Maps, Meet) are fine.
- System-wide memory pressure. Signal: YouTube crashes first because it uses the most memory, but if you leave other tabs open long enough, they eventually crash too, and your computer feels sluggish before it happens.
- An extension interfering with YouTube’s page scripts. Signal: the crash disappears in a new Incognito window with extensions off, or it only started after you installed or updated an ad blocker or video-download extension.
- A conflict introduced by a recent OS or antivirus update. Signal: the crashes started right after a Windows update, macOS update, or an antivirus product update, and were not happening before that.
How to tell which one you have
Before trying fixes, spend two minutes narrowing it down using Chrome’s own task manager, which is separate from your operating system’s and shows what each tab and process is using.
- Press Shift+Esc while Chrome is focused (or open the three-dot menu > More tools > Task manager).
- Play a YouTube video and watch the GPU process row. If its memory climbs sharply and the tab dies right as it peaks, this points to the GPU or decoder branch.
- Open a new Incognito window (Ctrl+Shift+N on Windows/ChromeOS, Cmd+Shift+N on Mac) and load the same video. Extensions are off there by default. If it plays fine, an extension is the cause.
- If neither of those isolates it, open several other heavy tabs alongside YouTube and see whether they crash too, in which case it is memory pressure, not YouTube specifically.
Fix: GPU or video-decoder conflict
This is the most common cause when the crash ties directly to video playback. Chrome hands decoding to your graphics driver whenever it can, and a driver that mishandles a codec will crash the tab instead of just glitching.
- Go to chrome://settings/system and turn off Use graphics acceleration when available. Relaunch Chrome when prompted.
- Load the same YouTube video again. If it now plays without crashing, your graphics driver is the cause. You can leave hardware acceleration off, or update your graphics driver through your OS or the manufacturer’s site and turn acceleration back on afterward.
- If it still crashes with acceleration off, go to chrome://flags, search for hardware-accelerated video decode, and set it to Disabled.
Changing entries on chrome://flags can affect other pages that rely on hardware decoding, like video calls. If something else breaks afterward, return to that flag and set it back to Default.
Fix: system-wide memory pressure
If other tabs eventually crash too, your device is running low on memory, and the operating system is closing whichever process uses the most, usually the tab playing video.
- Close tabs and apps you are not using. Chrome’s task manager (Shift+Esc) will show you which tabs are using the most memory so you know which to close first.
- Go to chrome://extensions and disable any extension you do not actively need. Extensions run in the background on every tab, including ones you are not looking at.
- If you use many YouTube tabs at once, turn on Chrome’s built-in Memory Saver under chrome://settings/performance, which frees memory from tabs you are not currently viewing.
- If the crashes only started recently and your device is otherwise healthy, restart it. A long-running session with many browser sessions and apps accumulates memory that is not released until you reboot.
Fix: an extension is interfering
If Incognito mode fixed it, one of your extensions is the cause. Some ad blockers and video-download tools inject scripts directly into YouTube’s page, and a script that does not match YouTube’s current page structure can crash the tab instead of failing quietly.
- Go to chrome://extensions and toggle every extension off.
- Reload YouTube and confirm it is stable.
- Turn extensions back on one at a time, reloading YouTube after each one, until the crash comes back. That is the culprit.
- Update that extension to its latest version, or remove it if no update is available.
Fix: a recent update introduced a conflict
If the crashes began right after a Windows, macOS, or antivirus update, treat the update as a suspect first. Antivirus products that hook into the browser process have caused this exact symptom after their own updates.
- Temporarily disable real-time or web-shield scanning in your antivirus software, then reload YouTube. Only do this briefly, and turn it back on afterward.
- Check whether your antivirus vendor has released a newer version since the crash started. Update it if so.
- If disabling antivirus fixes it and no update is available, add Chrome as an exception in the antivirus software’s settings instead of leaving protection off.
Editing antivirus or firewall exceptions changes what your security software is allowed to skip. Only exempt Chrome itself, not a whole folder, and only if you trust the source of your Chrome installation.
What does not fix this
These are the fixes people try first because they are easy, and in this specific case they usually do not hold.
- Clearing cache and cookies. This clears stored site data, not the GPU or decoder pipeline. If your cause is hardware decoding or memory pressure, a cleared cache changes nothing, and the crash returns as soon as you load a video again.
- Reinstalling Chrome. A reinstall replaces Chrome’s program files, but your graphics driver, your antivirus software, and your extensions all live outside that folder and get reinstalled right along with your profile. If any of those is the actual cause, it survives the reinstall untouched.
- Ending the tab in Task Manager and reopening it. This clears the immediate crash but not the underlying trigger. If the cause is a GPU conflict or memory pressure, the same tab will crash again within minutes because nothing about the environment changed.
Frequently asked questions
Why does Chrome only crash on YouTube and not other video sites?
YouTube plays more demanding video, at higher bitrates and resolutions, than most other sites, so it is often the first page to hit a GPU or memory limit that a lighter site never reaches. The underlying cause is rarely something YouTube itself did; it is that YouTube is the most demanding tab you regularly keep open.
I can only use YouTube for a few minutes before it crashes. Is that the same issue?
Yes. A short window before the crash is a common pattern with the GPU or decoder branch above, since memory or driver strain builds up gradually during playback rather than failing instantly. Start with the Task Manager check to confirm the GPU process is the one climbing.
Does uninstalling and reinstalling Chrome ever help with this?
Rarely, and only if a Chrome program file was itself corrupted, which is uncommon. For the GPU, memory-pressure, extension, and update-conflict causes above, a reinstall does not touch the part that is actually failing. Try the branch-specific fix first.
If nothing here works
Try a Guest session on the same computer. If YouTube is stable there, the cause lives in your main profile’s settings or extensions rather than your hardware.
A YouTube tab that crashes while every other site works fine almost always traces back to video decoding, memory limits, or an extension, not a broken Chrome install. Isolate which branch you are in first, then apply the matching fix instead of working through a generic list.
