Bug 269925 – [Reporting API] Consider supporting crash reports via the reporting API.

• Component: New Bugs
• Status: NEW

[Ryan Reno]

It may be useful to report when a process crashes due to, e.g. jetsams, via the reporting API if a web site opts in.

[Radar WebKit Bug Importer]

<rdar://problem/123454140>

[Tyler Gross]

It would be useful to Photoshop Web to be able to send crash reports in the event that the nature of the crash prevents JavaScript analytics from being processed, such as in the case of an out of memory crash.

[Sam Sneddon [:gsnedders]]

*** Bug 288525 has been marked as a duplicate of this bug. ***

Please implement this, or update the MDN page (https://developer.mozilla.org/en-US/docs/Web/API/Reporting_API) to denote the gap in support. This caused our team to miss OOM crashes that only exist in WebKit.

[Brent Fulgham]

(In reply to rai.o from comment #4)
> Please implement this, or update the MDN page
> (https://developer.mozilla.org/en-US/docs/Web/API/Reporting_API) to denote
> the gap in support. This caused our team to miss OOM crashes that only exist
> in WebKit.

Were these bugs in an iOS app that used WebKit, or in a web-based app running in Safari? (Or maybe even something in Linux)?

If a specific website was affected, I can use that to increase the weighting of prioritizing this.

Thanks!

[Ryan Reno]

(In reply to rai.o from comment #4)
> Please implement this, or update the MDN page
> (https://developer.mozilla.org/en-US/docs/Web/API/Reporting_API) to denote
> the gap in support. This caused our team to miss OOM crashes that only exist
> in WebKit.

Crash reporting is a non-standard extension to the Reporting API. The spec is incomplete and not implementable as written.

https://wicg.github.io/crash-reporting/

[Ryan Reno]

Also, I should refer readers of this bug to WebKit's position
https://github.com/WebKit/standards-positions/issues/456

Thanks for the context. The Reporting API documentation mentions crash reporting as a capability, but the browser compatibility information doesn’t make it immediately clear that crash reporting (via CrashReportBody) is only supported in Chromium-based browsers. Adding a prominent browser compatibility note or callout in the ‘Occurrence of crashes’ section would help developers understand implementation limitations upfront and avoid building features around unsupported functionality.

This missing OOM detection capability directly impacts user experience on WebKit browsers, forcing us to implement suboptimal workarounds that degrade functionality. Having this feature would enable us to provide equivalent experiences across all browsers and better serve our WebKit users.

This is for a web-based app running in any browser using WebKit under the hood. 

Reported the specific memory issue we discovered from a direct user report here: https://bugs.webkit.org/show_bug.cgi?id=300780