Open
Bug 1391586
Opened 8 years ago
Updated 2 years ago
Ability to break on endless content JS loops, detect content JS endless loops
Categories
(DevTools :: Debugger, enhancement, P5)
DevTools
Debugger
Tracking
(firefox57 affected)
NEW
Tracking | Status | |
---|---|---|
firefox57 | --- | affected |
People
(Reporter: mayhemer, Unassigned)
References
(Blocks 1 open bug)
Details
Chrome doesn't have this. But they at least offer to kill the page. We just hang and one has to find and kill the offending content process.
But there it ends. To find the loop cause in a debugger is impossible! Both chrome and fx don't allow opening devtools with the js debugger when there is a loop like this.
A killer feature would be to detect the loop (after say 30 or more seconds) and offer opening the debugger paused somewhere in the js code that is causing the loop.
Updated•7 years ago
|
Product: Firefox → DevTools
Updated•6 years ago
|
Blocks: dbg-control
Priority: -- → P5
Comment 1•5 years ago
|
||
That's a nice feature. I could see it being helpful for understanding why we entered the loop.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•