[Webkit-unassigned] [Bug 51393] New: Web Inspector: is missing the ability to reliably halt all javascript execution
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Tue Dec 21 06:20:38 PST 2010
https://bugs.webkit.org/show_bug.cgi?id=51393
Summary: Web Inspector: is missing the ability to reliably halt
all javascript execution
Product: WebKit
Version: 528+ (Nightly build)
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: Web Inspector
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: spamfaenger at gmx.de
CC: timothy at apple.com, rik at webkit.org, keishi at webkit.org,
pmuellr at yahoo.com, joepeck at webkit.org,
pfeldman at chromium.org, yurys at chromium.org,
bweinstein at apple.com, apavlov at chromium.org,
loislo at chromium.org
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.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list