342136 - DOM nodes view blank

Status: RESOLVED WORKSFORME

(Other Applications :: DOM Inspector, defect)

Description

[Simon Montagu :smontagu]

In a trunk build from this morning the DOM nodes view comes up blank. This is a recent regression, maybe from bug 210246

Comment 1

[Simon Montagu :smontagu]

From error console:
Error: [Exception... "Could not convert JavaScript argument"  nsresult: "0x80570009 (NS_ERROR_XPC_BAD_CONVERT_JS)"  location: "JS frame :: chrome://inspector/content/viewers/dom/dom.js :: DOMViewer :: line 86"  data: no]
Source File: chrome://inspector/content/viewers/dom/dom.js
Line: 86

Comment 2

[Dave Townsend [:mossop]]

Fine here

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060620 Minefield/3.0a1 ID:2006062005

Comment 3

[Boris Zbarsky [:bzbarsky]]

I tried backing out bug 210246 and that didn't help...

This is blocking me working on at least two bugs, so it'd really be nice to get some traction here.  :(

Comment 4

[Boris Zbarsky [:bzbarsky]]

So I bet this is a consequence of a dep build after the inspector move -- I'm seeing QI to nsITreeView fail on an inDOMView over here, with the inDOMView code living in libinspector.so....  I'll try clobbering.

Comment 5

[Benjamin Smedberg]

Most likely: libinspector.so shouldn't exist any more

Comment 6

[Boris Zbarsky [:bzbarsky]]

Yeah, clobbering helps...

Comment 7

[Simon Montagu :smontagu]

Clobbering helps for me too, so I suppose I can close this, but I wish it could have been avoided :(

Comment 8

[Christian :Biesinger (don't email me, ping me on IRC)]

it might've been enough to delete libinspector.so?

Comment 9

[Boris Zbarsky [:bzbarsky]]

It wasn't.  I tried that.

Comment 10

[Philip Chee]

Note for the enduser who doesn't know what a clobber build means:

1. Shutdown SeaMonkey/Firefox/whatever.
2. In the application components directory:
2.1. Delete inspector.dll or libinspector.so or libinspector.dylib
2.2. Delete compreg.dat/xpti.dat
3. Restart.