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 Report-To header (and only the Report-To header, no other header required), asynchronously.
The Report-To response header:
Report-To: {"group":"default","max_age":1800,"endpoints":[{"url":"https://guild.has.report/report"}],"include_subdomains":true}group: the name of the group, can be used in a CSP header in thereport-todirective, for examplemax_age: how long the browser should use the endpoint and report errors to it-
endpoints: reporting endpoint configuration, can specify multiple endpoints but reports will be sent to just one of themurl: where to send reports to, must behttps://, otherwise the endpoint will be ignored
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, possibly grouped with other reports (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 in
max_ageseconds after receiving theReport-Toheader, reload the page first to make sure it does (you'll want to use biggermax_agein your real header) - 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)
Related specs & documents
- Reporting API Working Draft
- Reporting API Editor's Draft (which will evolve into a Working Draft, followed by a Recommendation eventually)
-
Notable changes in the Editor's Draft are switching to structured headers (
Reporting-Endpointsinstead ofReport-To) and moving out concrete reports into the following separate Draft Community Group Reports: Crash Reporting, Deprecation Reporting, Intervention Reporting