I'm a little hesitant in the public API requiring browserStackParser, but I guess there's no good way around this.

We should pull stack parsing for now since:

• Origin trials should not be used with all users in production
• It might never make it to production Chrome
• I haven't managed to get it working

I also think handleReportingApi should be captureX instead. What do you think?

Yep, much better!

We should pull stack parsing for now since:

• I haven't managed to get it working

I've managed to get this working in an Electron application. Here's what was required:

• Add document-policy: include-js-call-stacks-in-crash-reports response header to page
• Launch Chromium with --enable-features=DocumentPolicyIncludeJSCallStacksInCrashReports flag

From reading the browser and renderer process code, I believe this should be enough to send the call stacks. So far this data has been valuable for us so I'd love to see it supported in Sentry!

One more thing to note. DevTools needs to be closed for the renderer to become unresponsive and send the call stack. I wrote this snippet to test.

function startInfiniteLoop () {
 console.log('spinning');
 while (1) {
 document.documentElement.getBoundingClientRect();
 }
}
// Click the document to start the infinite loop
document.documentElement.addEventListener('click', function clickHandler () {
 startInfiniteLoop();
});

@samuelmaddock could Electron pass the stack trace through in the webContents unresponsive event?

I haven't looked at the code, I'm simply guessing it uses similar code paths to triggering the Reporting API unresponsive events

@timfish I started working on this in electron/electron#44204

I'm hoping to get back to that PR soon. The call stacks use a separate async request so Electron may need to delay unresponsive to wait for that data if that's the design we go with.

什么时候可以被合并?
When can it be merged?

@cloudcome this is not prioritzed at the moment given we have some other things to get done first. We'll push this forward when this becomes a priority again. Thanks for your patience in the mean time.