Ready for Developer Testing: Call stacks in crash reports from unresponsive web pages

165 views
Skip to first unread message

Issack John

unread,
May 3, 2024, 2:33:18 PMMay 3
to blin...@chromium.org
Contact emails
Explainer
Specification
None

Design docs
Summary
This feature captures the JS call stack when a web page becomes unresponsive due to JavaScript code running an infinite loop or other very long computation. This helps developers to identify the cause of the unresponsiveness and fix it more easily. The JS call stack is included in the crash reporting API when the reason is unresponsive.


Blink component
TAG review
None

TAG review status
Pending

Risks


Interoperability and Compatibility
None


Gecko: No signal

WebKit: No signal

Web developers: No signals

Other signals:

Security
Stack frames from cross-domain scripts that were not loaded with CORS must be omitted.


WebView application risks
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None


Goals for experimentation
Looking for expressions of support for the API from people who have actually used it on their local machines. If they can explain what they were able to do with the feature that they couldn't do before, that's even better.

Ongoing technical constraints
None


Debuggability
Developers can launch DevTools, go to the "Application" Tab, then in the "Background services" section click on "Reporting API" where they can inspect reports that are queued to be sent. Application --> Reporting API


Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?
No

Is this feature fully tested by web-platform-tests?
No

DevTrial instructions
Flag name on chrome://flags


Finch feature name
DocumentPolicyIncludeJSCallStacksInCrashReports

Requires code in //chrome?
False

Tracking bug
Estimated milestones
DevTrial on desktop
125


Link to entry on the Chrome Platform Status
Links to previous Intent discussions
This intent message was generated by Chrome Platform Status.

Reply all
Reply to author
Forward
0 new messages