945749 - The Inspector is empty after a few page reloads

Status: RESOLVED DUPLICATE of bug 983386

(DevTools :: Inspector, defect)

Description

[Xavier Coulon]

Attachment: Screen Shot 2013-12-03 at 4.26.50 PM.png

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:25.0) Gecko/20100101 Firefox/25.0 (Beta/Release)
Build ID: 20131112160018

Steps to reproduce:

Using FF 25.0.1 on MacOSX 10.7. This problem did not occur with FF 25.0.0 or previous versions.
Working on an html page served by a local HTPT Server. Using the DOM Inspector to check some elements.



Actual results:

After a few page reloads, the DOM Inspector shows is empty.


Expected results:

The DOM Inspector should have show the actual DOM

Comment 1

[Xavier Coulon]

Closing and reopening the Developer Tools fixed the problem, which occurs again after a few page reloads.

Comment 2

[Sven]

I experience the same behavior with Firefox 26 on Mac OS X 10.9. It is reproducable every time but only for sites served on localhost e.g. with a Rails app:

* open http://localhost:3000
* DOM inspector works
* page reload
* DOM inspector is blank, breadcrumbs work fine

Comment 3

[Xavier Coulon]

Sven,

That's right, I have the issue with site running on localhost. I forgot to mention that in the bug description.

Comment 4

[[:Aleksej]]

bug 965058 may have been related.

Comment 5

[Rob Campbell [:rc] (:robcee)]

is this still happening? We should close this if we can't reproduce it.

Comment 6

[Xavier Coulon]

@robcee,

Right, it does not seem to happen anymore on FF 27.0.1.

thanks !

Comment 7

[Brian Grinstead [:bgrins]]

Sounds like this was resolved by 27 at the latest.  This could have also been related to Bug 909121 which was uplifted to 25, or Bug 922125, which cleaned up the markup view during page navigation and landed in 27.

Comment 8

[Xavier Coulon]

@bgrins, @robcee
I'd like to reopen this bug because it still occurs to me today :-(
I'm afraid my verification ~10 days ago was performed too fast.

Comment 9

[Brian Grinstead [:bgrins]]

(In reply to Xavier Coulon from comment #8)
> @bgrins, @robcee
> I'd like to reopen this bug because it still occurs to me today :-(
> I'm afraid my verification ~10 days ago was performed too fast.

Which browser version is it still happening with - 27?  Any chance you could check with Nightly or Aurora?

Comment 10

[Xavier Coulon]

Sorry, I forgot to mention that: I'm on FF 27.0.1.
I'll try with FF 28 Beta

Comment 11

[Mark Ellis]

I have this issue with ff 29.0.1, it's really annoying, so much so that I'm going back to firebug :(

Comment 12

[Brian Grinstead [:bgrins]]

(In reply to m from comment #11)
> I have this issue with ff 29.0.1, it's really annoying, so much so that I'm
> going back to firebug :(

Since you are bumping into this, do you have steps to reproduce this problem?  This would be very helpful for tracking it down and getting it fixed.

Comment 13

[Mark Ellis]

sure. i've attached a webpage that does it, if you inspect one of the categories text inputs, and reload the page, it'll be blank, or at least it is for me.

Comment 14

[Mark Ellis]

Attachment: broken_inspector.tar.bz2

page that breaks the inspector, see https://bugzilla.mozilla.org/show_bug.cgi?id=945749#c13

Comment 15

[Mark Ellis]

also i'm on archlinux
Linux mark-work 3.14.4-1-ARCH #1 SMP PREEMPT Tue May 13 16:41:39 CEST 2014 x86_64 GNU/Linux
firefox 29.0.1

Application: Firefox 29.0.1 (20140514164129)
Operating System: Linux (x86_64-gcc3)

- Adblock Plus 2.6
- British English Dictionary 1.19.1
- Extension List Dumper 1.15.2 (just added to get this list)
- Firebug 1.12.8
- Greasemonkey 1.15
- LastPass 3.1.1
- Live HTTP headers 0.17
- User Agent Switcher 0.7.3
- Web Developer 1.2.5
- YSlow 3.1.8

Comment 16

[Brian Grinstead [:bgrins]]

(In reply to m from comment #13)
> sure. i've attached a webpage that does it, if you inspect one of the
> categories text inputs, and reload the page, it'll be blank, or at least it
> is for me.

Ah, I see.  This problem is resolved in Bug 1002280 (it is fixed in Nightly builds).  I will see if we can uplift that fix to Aurora to get it released faster

Comment 17

[Brian Grinstead [:bgrins]]

I think there are a couple of different causes here. The issue from Comment 13 is a dup of bug 1002280 (which I'm requesting uplift for), the issue from Comment 2 is a dup of Bug 983386.

Comment 18

[Brian Grinstead [:bgrins]]

(In reply to Mark Ellis from comment #11)
> I have this issue with ff 29.0.1, it's really annoying, so much so that I'm
> going back to firebug :(

Mark, if you download a copy of aurora (https://www.mozilla.org/en-US/firefox/channel/#aurora) you will get this fix (and other new features) quite a bit faster.  The issue you are running into is also currently fixed in Nightly builds: https://nightly.mozilla.org/.

Comment 19

[[e-mail]]

Hello, this issue is still remaining in Firefox 37.0a2 (2015-02-04)developer edition with those only activated extensions :
Adblock Plus 2.6.7
Auto Reload 1.20
Feedly 16.0.528
Firefox Developer Tools Adapters 0.2.4
Web developer 1.2.5

Comment 20

[Maël Lavault]

Happens to me on every page reload with a react isomorphic app and Firefox 47 (also did the same with 45 and 46). It is so frustrating to spend my day closing and reopening devtools.

Comment 21

[Brian Grinstead [:bgrins]]

(In reply to mael.lavault from comment #20)
> Happens to me on every page reload with a react isomorphic app and Firefox
> 47 (also did the same with 45 and 46). It is so frustrating to spend my day
> closing and reopening devtools.

Hi, is there any way you could point to the URL of a page where you see this?

Comment 22

[Maël Lavault]

Hi,

No I'm sorry it is our company website rewrite which is not live now.

I will try to find other pages affected, I already experienced it on many pages (but not all).

I can make a screencast to show the problem, would that help ?

Comment 23

[Patrick Brosset <:pbro>]

A screencast would help, yes, but also copying the errors you see in the browser console (ctrl+shift+J) when the problem occurs.
Of course if you can find other pages that are affected, that would be perfect!
Thanks for your help.

Comment 24

[Maël Lavault]

Attachment: Screencast_06-16-2016_10:22:01 AM.webm

Here is the screencast.

So I just made a little change to the source code, the local server restart automatically and then I refresh the page. You can see the inspector staying blank.

Comment 25

[Maël Lavault]

I get those errors in browser console :

(not sure if they are related)

TypeError: can't access dead object
Stack trace:
WalkerActor<.documentElement<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/server/actors/inspector.js:1632:1
actorProto/</handler@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/server/protocol.js:1013:19
DSC_onPacket@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/server/main.js:1643:15
LocalDebuggerTransport.prototype.send/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/transport/transport.js:569:11
exports.makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/ThreadSafeDevToolsUtils.js:101:14
exports.makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/ThreadSafeDevToolsUtils.js:101:14
 protocol.js:907
Protocol error (unknownError): TypeError: can't access dead object Promise-backend.js:940
TypeError: jsterm is null: passSelectedNode@resource://gre/modules/commonjs/toolkit/loader.js -> resource://react-devtools/main/trackSelection.js:46:9
trackSelection/</</<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://react-devtools/main/trackSelection.js:39:9
EventEmitter_emit@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/event-emitter.js:147:11
Selection.prototype.setNodeFront@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/framework/selection.js:185:5
InspectorPanel.prototype._onBeforeNavigate@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/inspector/inspector-panel.js:221:5
EventEmitter_emit@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/event-emitter.js:147:11
TabTarget.prototype._setupRemoteListeners/this._onTabNavigated@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/framework/target.js:487:9
eventSource/aProto.emit@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/client/main.js:131:9
DebuggerClient.prototype.onPacket@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/client/main.js:1012:7
LocalDebuggerTransport.prototype.send/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/transport/transport.js:569:11
exports.makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/ThreadSafeDevToolsUtils.js:101:14
exports.makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/ThreadSafeDevToolsUtils.js:101:14

 event-emitter.js:152:0
TypeError: jsterm is null: passSelectedNode@resource://gre/modules/commonjs/toolkit/loader.js -> resource://react-devtools/main/trackSelection.js:46:9
trackSelection/</</<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://react-devtools/main/trackSelection.js:39:9
EventEmitter_emit@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/event-emitter.js:147:11
Selection.prototype.setNodeFront@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/framework/selection.js:185:5
InspectorPanel.prototype._onBeforeNavigate@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/inspector/inspector-panel.js:221:5
EventEmitter_emit@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/event-emitter.js:147:11
TabTarget.prototype._setupRemoteListeners/this._onTabNavigated@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/client/framework/target.js:487:9
eventSource/aProto.emit@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/client/main.js:131:9
DebuggerClient.prototype.onPacket@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/client/main.js:1012:7
LocalDebuggerTransport.prototype.send/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/transport/transport.js:569:11
exports.makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/ThreadSafeDevToolsUtils.js:101:14
exports.makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/ThreadSafeDevToolsUtils.js:101:14

Comment 26

[Patrick Brosset <:pbro>]

Thanks for the screencast, so it's definitely a duplicate of bug 983386