Can't open exception source from the console

NEW
Unassigned

Status

P3
normal
5 years ago
2 months ago

People

(Reporter: msucan, Unassigned)

Tracking

(Blocks: 1 bug)

Trunk

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
Boris points us to:

http://www.jango.com/stations/263448187/tunein?gcid=1&l=0

which displays a bunch of warnings and one TypeError:

[18:33:28.080] TypeError: _jui.jango_player is undefined @ http://cd09.s3.static.jango.com/javascripts/proto_player_sm2_37808.js:855

If you try to click the exception source link bz reports that the debugger opens and it fails to show the script source, with a nightly from the 19th of April. I cannot reproduce that error with my local fx-team build of today. I get the debugger opened for a very short time then view source opens. With today's nightly bz gets a crash. He also reports that yesterday's nightly shows the same behavior as that on my system.

After I open the debugger on that page (via click on message source) I get a dbg-script-actors.js exception:

[18:33:24.846] [Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIChannel.asyncOpen]"  nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)"  location: "JS frame :: chrome://global/content/devtools/dbg-script-actors.js :: fetch :: line 2695"  data: no]
undefined @ chrome://global/content/devtools/dbg-server.js:608

Followed by the client-side error:

[18:33:24.848] Server did not specify an actor, dropping packet: {"error":"unknownError","message":"error occurred while processing 'source': [Exception... \"Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIChannel.asyncOpen]\"  nsresult: \"0x80040111 (NS_ERROR_NOT_AVAILABLE)\"  location: \"JS frame :: chrome://global/content/devtools/dbg-script-actors.js :: fetch :: line 2695\"  data: no]\nundefined"} @ resource://gre/modules/devtools/dbg-client.jsm:592

Conclusions until now:

1. fetch() is used to fetch sources and it fails to do so. Looks like a regression caused by source maps landing (this is new code to me, maybe there's a different root cause here).

2. the web console doesn't always handle gracefully cases when the debugger cannot display the script source.
As far as I can tell, the behavior changed in http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=50d25e083421&tochange=acf388eaf9e9 to go from "show nothing" to "switch to debugger panel showing nothing, open view source, switch back to console".
So I just tried building a debug build from rev acf388eaf9e9 and it has this problem, so the fact that it started working in a nightly is ... odd.
Oh, and I get:

[14:07:41.104] TypeError: can't access dead object
TA__addDebuggees@chrome://global/content/devtools/dbg-script-actors.js:139
TA_findGlobals@chrome://global/content/devtools/dbg-script-actors.js:153
TA_onAttach@chrome://global/content/devtools/dbg-script-actors.js:222
DSC_onPacket@chrome://global/content/devtools/dbg-server.js:655
LDT_send/<.run@chrome://global/content/devtools/dbg-transport.js:224
 @ chrome://global/content/devtools/dbg-server.js:608
[14:07:41.132] Server did not specify an actor, dropping packet: {"error":"unknownError","message":"error occurred while processing 'attach': TypeError: can't access dead object\nTA__addDebuggees@chrome://global/content/devtools/dbg-script-actors.js:139\nTA_findGlobals@chrome://global/content/devtools/dbg-script-actors.js:153\nTA_onAttach@chrome://global/content/devtools/dbg-script-actors.js:222\nDSC_onPacket@chrome://global/content/devtools/dbg-server.js:655\nLDT_send/<.run@chrome://global/content/devtools/dbg-transport.js:224\n"} @ resource://gre/modules/devtools/dbg-client.jsm:592
That is, I get that in a debug build from rev acf388eaf9e9.
Latent bug.
Priority: -- → P3
Just guessing here, but could this be related to bug 842937 in some way?

Updated

4 years ago
Summary: Can't open exception source from the Web Console → Can't open exception source from the console

Updated

4 years ago
Blocks: 1074592

Updated

2 months ago
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.