| Summary: | Web Inspector: console assertion when debugger pauses with native call frame in call stack | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | BJ Burg <bburg> | ||||||
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> | ||||||
| Status: | NEW --- | ||||||||
| Severity: | Normal | CC: | graouts, inspector-bugzilla-changes, webkit-bug-importer | ||||||
| Priority: | P2 | Keywords: | InRadar | ||||||
| Version: | WebKit Nightly Build | ||||||||
| Hardware: | All | ||||||||
| OS: | All | ||||||||
| Attachments: |
|
||||||||
Created attachment 259625 [details]
reduced testcase
|
Created attachment 259514 [details] Screenshot of relevant state In the case I captured in the screenshot, it appears that window.dispatchEvent is midway through the call stack. It has an invalid source location, triggering a console assert. We should be able to gracefully handle this case. It would be even better if native/builtins have their own color in the call stack sidebar section, but that's another issue.