Closed
Bug 1088153
Opened 10 years ago
Closed 10 years ago
console won't execute JavaScript while debugger paused at breakpoint
Categories
(DevTools :: Debugger, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1057031
People
(Reporter: offbynone, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:36.0) Gecko/20100101 Firefox/36.0 Build ID: 20141023030203 Steps to reproduce: Stop debugger at breakpoint, type some JavaScript into the console and hit enter. Actual results: Acts as if I hit shift + enter -- moves cursor to a new line. No JavaScript gets executed. Expected results: JavaScript should have been executed.
Reporter | ||
Comment 1•10 years ago
|
||
I can't seem to reliably reproduce this problem. When it happens usually closing the dev tools, reloading the page and re-opening the tools seems to fix the issue. The last time it happened I took a look at the browser console and saw this error: DevToolsUtils.js line 59 Handler function threw an exception: TypeError: info is null Stack: _addBreakpoint@resource://gre/modules/commonjs/toolkit/loader.js -> resource:///modules/devtools/sourceeditor/debugger.js:138:5 addBreakpoint/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource:///modules/devtools/sourceeditor/debugger.js:154:37 makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/DevToolsUtils.js:83:14 EventLoop.prototype.enter@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/script.js:410:5 ThreadActor.prototype._pushThreadPause@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/script.js:605:5 ThreadActor.prototype._pauseAndRespond@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/script.js:779:7 BreakpointActor.prototype.hit@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/script.js:4538:12
Comment 3•10 years ago
|
||
Does the error happen only after a reload? If so, this is a dupe of bug 1057031.
Comment 4•10 years ago
|
||
(In reply to Panos Astithas [:past] from comment #3) > Does the error happen only after a reload? If so, this is a dupe of bug > 1057031. Marking needinfo for Off By None
Flags: needinfo?(offbynone)
Reporter | ||
Comment 5•10 years ago
|
||
I am not entirely sure as I have been unable to reproduce the error reliably. I am not doing a ton of development over the next few weeks due to the holidays. I would say close the bug and if I find that I can get it to happen without a reload I will submit a new one.
Flags: needinfo?(offbynone)
Comment 6•10 years ago
|
||
(In reply to Off By None from comment #5) > I am not entirely sure as I have been unable to reproduce the error > reliably. I am not doing a ton of development over the next few weeks due > to the holidays. I would say close the bug and if I find that I can get it > to happen without a reload I will submit a new one. Thanks for following up, I think it's safe to assume this is the same problem as Bug 1057031 for now, but if you bump into it again feel free to reopen this one.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•