Crash reports with report-to
Sending reports about browser or tab (where tab means one of the browser processes) crashes with Reporting API using the Reporting-Endpoints header (and only the Reporting-Endpoints header, no other header required), asynchronously.
The Reporting-Endpoints response header:
Reporting-Endpoints: default="https://west.has.report/report"default: the name of the endpoint, crash reports are delivered to an endpoint namedcrash-reportingif specified, otherwise to an endpoint nameddefault"url": where to send reports, must behttps://, otherwise the endpoint will be ignored-
You may provide multiple
name="url"endpoints separated by comma (,)- For example:
Reporting-Endpoints: csp-reporting="https://example.com/csp", nel-reporting="https://example.com/nel"
- For example:
Try crashing your tab
You can simulate a crash by copying and pasting the following link into this tab's address bar: chrome://crash/ (in Chrome) – it's not clickable for a good reason 😈
- Will trigger a report that will be sent asynchronously (violation visible in Developer Tools in the Console tab, you won't see the report in Network tab but you can still view the reporting requests)
- …if the tab crashes after receiving the
Reporting-Endpointsheader, reload the page first to make sure it does - Check your reports (can take some time before the browser sends the report)
- Reports can contain an optional
reason, e.g.oom(Out-of-Memory, try with chrome://memory-exhaust/),unresponsive(killed due to being unresponsive, try with chrome://hang/ and wait)
Related specs & documents
- Reporting API Working Draft
- Reporting API Editor's Draft (which will evolve into a Working Draft, followed by a Recommendation eventually)
- Crash Reporting Draft Community Group Report