If Google Chrome unexpectedly closes, or if a specific tab suddenly displays the “Aw, Snap!” error page, you might wonder if a specific extension or a buggy website caused the crash. Chrome doesn’t show you detailed error logs by default; it simply crashes and restarts.
However, Chrome secretly generates detailed crash diagnostic files and stores them in a hidden local directory before (optionally) uploading them to Google. You can safely extract these hidden crash reports directly from the browser’s internal URL system to see a chronological list of every fatal error your browser has encountered.
How to Safely Extract Google Chrome Crash Reports
You must use Chrome’s internal URL system to access the hidden crash database.
- Open the Google Chrome browser.
- Click inside the top URL address bar, carefully type the following exact text, and press Enter:
chrome://crashes - You are now looking at the internal crash diagnostic page.
- If the page says “Crash reporting is disabled,” you must first click the link provided to enable crash reporting in your privacy settings, and then wait for the next crash to occur.
- If you see a list of crashes, they will be organized by date and time. Each entry will have a Local ID (a long string of numbers and letters).
- Click the small button that says Show developer details in the top right corner of the page.
This will expose the exact Local Crash Context and the specific module that failed. While the raw data is designed for Google engineers, you can often spot plain-text clues (like the name of a specific `.dll` file or a third-party extension ID) right next to the crash timestamp, allowing you to pinpoint which software plugin is bringing down your browser.