Bug 51393 - Web Inspector: missing the ability to reliably pause debugger in runaway JavaScript
Summary: Web Inspector: missing the ability to reliably pause debugger in runaway Java...
Status: UNCONFIRMED
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2010-12-21 06:20 PST by Martin Häcker
Modified: 2016-12-13 15:40 PST (History)
16 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Häcker 2010-12-21 06:20:37 PST 
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.
Comment 1 Yury Semikhatsky 2010-12-21 07:31:45 PST 
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.
Comment 2 Radar WebKit Bug Importer 2014-12-17 11:22:05 PST 
<rdar://problem/19281497>
Comment 3 Radar WebKit Bug Importer 2014-12-17 11:26:34 PST 
<rdar://problem/19281631>