269925 2024-02-22 10:17:52 -0800 [Reporting API] Consider supporting crash reports via the reporting API. 2025-10-15 18:52:31 -0700 1 1 1 Unclassified WebKit New Bugs Other Unspecified Unspecified NEW https://bugs.webkit.org/show_bug.cgi?id=300782 InRadar P2 Normal --- 1 rreno webkit-unassigned ap bfulgham rai.o rreno tylergross28 webkit-bug-importer yuta oldest_to_newest 2016109 0 rreno 2024-02-22 10:17:52 -0800 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. 2016112 1 webkit-bug-importer 2024-02-22 10:19:00 -0800 <rdar://problem/123454140> 2016178 2 tylergross28 2024-02-22 13:16:55 -0800 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. 2121799 3 gsnedders 2025-06-04 15:42:42 -0700 *** Bug 288525 has been marked as a duplicate of this bug. *** 2150851 4 rai.o 2025-10-14 07:38:13 -0700 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. 2150883 5 bfulgham 2025-10-14 09:39:00 -0700 (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! 2150900 6 rreno 2025-10-14 10:23:37 -0700 (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/ 2150901 7 rreno 2025-10-14 10:25:37 -0700 Also, I should refer readers of this bug to WebKit's position https://github.com/WebKit/standards-positions/issues/456 2151200 8 rai.o 2025-10-15 03:14:30 -0700 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