Closed
Bug 1052072
Opened 10 years ago
Closed 6 years ago
Pause on exceptions not working with reload
Categories
(DevTools :: Debugger, defect)
DevTools
Debugger
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: erik, Unassigned)
References
Details
Steps to reproduce:
1. Go to http://widget.centraltorpedos.com.br/gmaps/
2. Open Web Console
3. Notice that there was a script error on the page
4. Switch to the Debugger tab and make sure "Pause on exceptions" is checked.
5. Reload the page
Expected outcome
Break at the line that had the exception
Actual outcome
The debugger does not break. What is worse. The UI is now dead. I can no longer interact with the non chrome parts of the browser. (Right click does not work, keyboard shortcuts do not work etc)
Comment 2•10 years ago
|
||
Erik, thanks for the report. What version of firefox are you seeing this behavior?
I'm successfully pausing on the TypeError about this.impl being undefined in Nightly 34. Although, note that this is an eval'd script, and we don't fully support debugging them eval'd scripts yet. One result of that is that the line number is off for me. That should be fixed when bug 917579 lands, though.
Flags: needinfo?(nfitzgerald) → needinfo?(erik)
Updated•10 years ago
|
Component: JavaScript Engine → Developer Tools: Debugger
Product: Core → Firefox
Updated•10 years ago
|
Summary: Debugger is not working → Pause on exceptions not working with reload
Reporter | ||
Comment 3•10 years ago
|
||
I was using Nightly on Linux (from the date of the report).
Flags: needinfo?(erik)
Reporter | ||
Comment 4•10 years ago
|
||
Tried it in 34.0a1 (2014-08-13) and at least it does not hang the render view any more.
However, the debugger still does not pause for me. The error is reported to the console and no call stack has no stack frames to display.
Comment 5•10 years ago
|
||
Disabling source maps and auto-blackboxing gives me this:
ThreadSources.prototype.getOriginalLocation threw an exception: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data
Stack: SourceMapConsumer@resource://gre/modules/devtools/SourceMap.jsm:67:19
ThreadSources.prototype._fetchSourceMap/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/script.js:5043:19
resolve@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/deprecated-sync-thenables.js:40:40
then@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/deprecated-sync-thenables.js:20:43
resolve@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/deprecated-sync-thenables.js:72:11
resolve@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/deprecated-sync-thenables.js:40:11
then@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/deprecated-sync-thenables.js:20:43
resolve@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/deprecated-sync-thenables.js:72:11
fetch/streamListener.onStopRequest@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/script.js:5368:11
EventLoop.prototype.enter@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/script.js:410:5
ThreadActor.prototype.synchronize@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/script.js:1099:7
ThreadActor.prototype.onExceptionUnwind@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/script.js:2219:21
[...content page script frames...]
Comment 6•10 years ago
|
||
(In reply to Panos Astithas [:past] from comment #5)
> Disabling source maps and auto-blackboxing gives me this:
Hrm, we shouldn't even be fetching the source map in that case, troubling.
Updated•10 years ago
|
Blocks: dbg-exception
Updated•6 years ago
|
Product: Firefox → DevTools
Comment 7•6 years ago
|
||
This should be fixed now. Please let me know if you still see the problem.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•