Contact emails [email protected]
Explainer https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/CrashReporting/AddStackToCrashReports.md Specification No information provided Design docs https://docs.google.com/document/d/1lTlSzYSknbW9EuoR1pM2oSRqt66BmEVJ3tAnCKuaeM4/edit?usp=sharing Summary Out-of-memory crash reports can include a JavaScript call stack when a document opts in using Document-Policy: include-js-call-stacks-in-crash-reports. The stack helps developers group production OOM failures and identify the JavaScript execution path active near heap exhaustion. Capture is best effort and does not necessarily identify the allocation site or root cause. Blink component Chromium > Internals > Network > ReportingAndNEL Web Feature ID reporting-crashes Motivation Renderer OOM crashes are difficult to diagnose because they can depend on workload, data, and memory conditions and may not reproduce locally. Chromium provides a best-effort JavaScript stack for unresponsive renderer crash reports using the same Document Policy opt-in. Without comparable OOM stacks, developers receive only reason: "oom" and must correlate page URLs, application telemetry, user reports, and additional instrumentation to investigate the failure. Initial public proposal https://github.com/WICG/crash-reporting/issues/45 Goals for experimentation Requires code in //chrome? False Tracking bug https://issues.chromium.org/issues/358611259 Estimated milestones No milestones specified Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5111794608766976?gate=5103298190376960 This intent message was generated by Chrome Platform Status. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6a95b46b.96f907aa.2c2b5.014e.GAE%40google.com.
