Crash Reporting Demo

Crash reporting active — the browser will report any crash that occurs on this page

How to trigger a crash report

Unlike other report types, crashes cannot be triggered safely from JavaScript — you need to deliberately crash the tab

⚠️ Warning: The URLs below will immediately crash or hang your current tab. Make sure you have saved any work before proceeding. These are Chrome-specific internal URLs — browsers block them from being opened via links, so you must copy and paste them into the address bar manually.

crash Tab crash

Immediately crashes the renderer process for the current tab. The browser will show its crash page ("Aw, Snap!") and queue a crash report for delivery.

chrome://crash/

oom Out of memory

Exhausts available memory for the current tab, triggering an out-of-memory crash. The report will include "reason": "oom" to distinguish it from a regular crash.

chrome://memory-exhaust/

hang Unresponsive tab

Hangs the renderer process indefinitely. The browser detects the unresponsiveness and generates a report with "reason": "unresponsive" after a timeout.

chrome://hang/

Reporting-Endpoints header sent with this page

Reporting-Endpoints: default="https://helios.report-uri.com/a/t/g"

How crash reporting works

The browser registers the Reporting-Endpoints endpoint when the page loads. If the tab crashes, the browser — not the crashed tab — queues a crash report and delivers it on the next available opportunity. Because the report is generated and sent by the browser process itself, it works even when the page's JavaScript is completely dead. This gives you real-world crash visibility across your entire user base with no additional instrumentation required.

Example crash report payload (sent by the browser)

[{
  "age": 0,
  "type": "crash",
  "url": "https://report-uri-demo.com/crash/",
  "body": {
    "reason": "oom"
  }
}]

Possible values for reason

""             — generic crash (renderer process terminated unexpectedly)
"oom"          — out of memory
"unresponsive" — tab was killed after becoming unresponsive