Bug 167083
| Summary: | Web Inspector: capture async stack trace when web content calls addEventListener, window.postMessage, fetch, XHR.send | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Blaze Burg <bburg> |
| Component: | Web Inspector | Assignee: | Matt Baker <mattbaker> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | Normal | CC: | inspector-bugzilla-changes, mattbaker, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | All | ||
| OS: | All | ||
Blaze Burg
We should capture for more async script initiators. These are all for DOM methods.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/30033664>
Matt Baker
It looks like DOMWindow already saves the call stack on postMessage (WebCore/page/DOMWindow.cpp:980), so long as the console agent is enabled. This is done so that if a target origin error occurs the console error can include a call stack.
Instead of saving the call stack in the PostMessageTimer, DOMWindow should look up the current async stack trace using the InspectorDebuggerAgent.
Matt Baker
Closing. This has been split into the following:
Web Inspector: capture an async stack trace when web content calls addEventListener
<https://webkit.org/b/174739>
Web Inspector: capture async stack trace when workers/main context posts a message
<https://webkit.org/b/167084>
Web Inspector: capture async stack trace when web content calls fetch, XHR.send
<https://webkit.org/b/174742>