Bug 51393
| Summary: | Web Inspector: missing the ability to reliably pause debugger in runaway JavaScript | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Martin Häcker <spamfaenger> |
| Component: | Web Inspector | Assignee: | Nobody <webkit-unassigned> |
| Status: | UNCONFIRMED | ||
| Severity: | Normal | CC: | apavlov, ap, bweinstein, ggaren, graouts, inspector-bugzilla-changes, jonowells, keishi, loislo, mark.lam, oliver, pfeldman, pmuellr, rik, webkit-bug-importer, yurys |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | All | ||
| OS: | All | ||
Martin Häcker
If some code is running away (in a clever way) there is no way to stop and inspect that code in the web inspector as it itself is blocked by that code.
Reasons this can happen: Code that consumes a lot of memory (but without hitting the js limits), sets lots of timeouts (so each javascript timeout that you acknowledge is immediately followed by more processing).
This needs to change. The debugger needs to be able to always and reliably (and with low latency) be able to stop javascript exectuion.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Yury Semikhatsky
This should be possible in Chromium where the front-end runs in its own process different from that of the inspected page and can pause current script even if it's in a tight loop.
Radar WebKit Bug Importer
<rdar://problem/19281497>
Radar WebKit Bug Importer
<rdar://problem/19281631>