The Script panel does not show any script when reopening Firebug in Fx 39 #7918

Closed
fflorent opened this Issue Jun 22, 2015 · 19 comments

Projects

None yet

7 participants

@fflorent
Member

STR:

  1. Open Firebug on this page
  2. Enable and select the Script panel
  3. Close Firebug
  4. Reopen Firebug => Bug : the script panel is reporting that there is no script on this page

Firefox version: 39 or newer
Firebug version: 2.0.11

I see this exception when the bug happens:

onPacket threw an exception: Error: Server did not specify an actor, dropping packet: {"error":"unknownError","message":"error occurred while processing 'attach: TypeError: docShell is null\nStack: getChildDocShells@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/webbrowser.js:53:7\nTabActor.prototype.docShells@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/webbrowser.js:722:12\nTabActor.prototype.windows@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/webbrowser.js:743:5\nTabActor/this.makeDebugger<.findDebuggees@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/webbrowser.js:663:26\nmakeDebugger/dbg.addDebuggees@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/utils/make-debugger.js:78:24\nThreadActor.prototype.onAttach@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/script.js:676:5\nDSC_onPacket@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/main.js:1459:15\nLocalDebuggerTransport.prototype.send/<@resource://gre/modules/devtools/dbg-client.jsm -> resource://gre/modules/devtools/transport/transport.js:561:11\nmakeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/DevToolsUtils.js:82:14\nmakeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/DevToolsUtils.js:82:14\nLine: 53, column: 6"}
Stack: DebuggerClient.prototype.onPacket@resource://gre/modules/devtools/dbg-client.jsm:944:1
LocalDebuggerTransport.prototype.send/<@resource://gre/modules/devtools/dbg-client.jsm -> resource://gre/modules/devtools/transport/transport.js:561:11
makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/DevToolsUtils.js:82:14
makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/DevToolsUtils.js:82:14
Line: 944, column: 0

Florent

@fflorent fflorent changed the title from The Script panel does not show any script when reopening Firebug to The Script panel does not show any script when reopening Firebug in Fx 39 Jun 22, 2015
@SebastianZ
Member

FWIW a question on Stack Overflow sounds related and I think I already read this in the discussion group as well. Sounds like this error should get high priority, because it completely breaks JS debugging.

Sebastian

@fflorent
Member

I can't reproduce it on my machine at home, but just at work.

That's pretty weird. If others encounter that issue, I should work on it.

Florent

@SebastianZ
Member

According to the discussion group and Stack Overflow many people are affected by this bug.
And I can also reproduce it easily.

The error mentioned above is preceded by another one:

error occurred while processing 'attach: TypeError: docShell is null
Stack: getChildDocShells@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/webbrowser.js:53:7
TabActor.prototype.docShells@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/webbrowser.js:722:12
TabActor.prototype.windows@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/webbrowser.js:743:5
TabActor/this.makeDebugger<.findDebuggees@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/webbrowser.js:663:26
makeDebugger/dbg.addDebuggees@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/utils/make-debugger.js:78:24
ThreadActor.prototype.onAttach@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/actors/script.js:676:5
DSC_onPacket@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/server/main.js:1459:15
LocalDebuggerTransport.prototype.send/<@resource://gre/modules/devtools/dbg-client.jsm -> resource://gre/modules/devtools/transport/transport.js:561:11
makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/DevToolsUtils.js:82:14
makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://gre/modules/devtools/DevToolsUtils.js:82:14
Line: 53, column: 6

Sebastian

@fflorent
Member

I'll take a look at it tomorrow (at work). I still can't reproduce it at home, really weirdly.

I guess you don't have any extension installed?

Florent

@SebastianZ
Member

I guess you don't have any extension installed?

I tested it on a clean profile with just Firebug installed. What OS do you use at work?

Sebastian

@fflorent
Member

Also Linux Debian... Weirdfirebug/firebug a écrit :
I guess you don't have any extension installed?

I tested it on a clean profile with just Firebug installed. What OS do you use at work?

Sebastian

—Reply to this email directly or view it on GitHub.

@blockjon
blockjon commented Aug 3, 2015

I'm working on an app that uses angular js. I'm unable to see the scripts in my javascript console either. Strangely, I can see the scripts if I restart Firefox and go to the front page of my app. However, after I do a facebook login (via the oauth redirect flow), when I return to my app, the scripts return to a state of not appearing in the javascript console and all i see is "No javascript on this page".

MacOS running Firefox 39, Firebug 2.0.11.

@chilipepper987

I only get this at work as well. However, I just clear the console when it shows up, and debugging works fine

@janodvarko janodvarko self-assigned this Aug 5, 2015
@janodvarko
Member

I did some analysis of the problem and it rather looks like a platform issue introduced in Fx 39 and fixed in Fx40+

Since Firefox 40 will be released next week (August 11) I don't see much reasons to spend more time on it now.

Assigning to myself anyways.

Honza

@fflorent
Member
fflorent commented Aug 5, 2015

Indeed. I don't have this issue anymore after the update of my Firefox beta.

Florent

@SebastianZ
Member

Note that Firefox 41 reintroduces this issue in a slightly different way. It works fine when closing and reopening Firebug, though not when reloading the page.

In the browser console I see the following error:

NS_ERROR_IN_PROGRESS: Component returned failure code: 0x804b000f (NS_ERROR_IN_PROGRESS) [nsICacheEntry.dataSize] netCacheReader.js:283:0

Sebastian

@fflorent
Member

Regression range : https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=bda3c545aa48&tochange=d12f46ccb758

I don't have time to guess what's the regression commit.

Florent

@janodvarko
Member

@fflorent thanks for the regression range
it's this one: https://hg.mozilla.org/integration/mozilla-inbound/rev/152f968b6b13

Patch committed

Can anybody verify please?

Honza

@janodvarko janodvarko closed this Aug 10, 2015
@fflorent
Member
@SebastianZ
Member

I can confirm that it's working again. Thank you Honza!

Sebastian

@moyarich
moyarich commented Nov 19, 2016 edited

this is broken again on firefox 50.0, Firebug 2.0.18

firefox has been updated on all my computers from version 49.0 to 50.0. firebug worked fine on 49.0

well since firebug stopped working. i uninstalled it and decided to use the firebug theme for the builtin firefox developer tool. http://www.ghacks.net/2016/04/21/firebug-theme-firefox-developer-tools/

@ray-moravian

unfortunately, it is....my ff just got upgraded to .50 and instantly firebug script tab shows only this...

@SebastianZ
Member

As @moyarich just wrote, Firebug will stop working soon. The Firebug team suggests to use the Firefox DevTools instead. Move info can be found at https://blog.getfirebug.com/2016/06/07/unifying-firebug-firefox-devtools/.

Sebastian

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment