203369 - DOM inspector crashes when viewing nodes of pages no longer in browser

Status: RESOLVED DUPLICATE of bug 111411

(Other Applications :: DOM Inspector, defect)

Description

[Stevie-O]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030401
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030401

When viewing the various Object Properties of a node that was in a page that is
no longer being displayed by Mozilla, Mozilla dies a slow, painful death.

Reproducible: Always

Steps to Reproduce:
1. Go to http://www.mozilla.org/.  Easy for those of us who haven't bothered to
change from the default homepage :)
2. In that same window, then browse too http://www.google.com/.
3. Once Google has loaded, use the DOM inspector to view the Object properties
of one of the nodes (preferably an HTML element) in the page document itself
(this is much easier with the Sidebar version, since it doesn't let all the
toolbars and such get in the way). Select a node so that you can see its
properties in the "Object" frame on the right.
4. Go back to the main browser window and click 'Back' in order to return to the
Mozilla page.
5. Go back to the DOM inspector window.  The Object frame has an icon that lets
you select among DOM node, Box Model, XBL Bindings, CSS Style Rules, Computed
Style, and JavaScript Object.  Your choices here may be limited, depending on
what node you selected (this is why the HTML elements are best -- they have the
most options).  Click that button and change the view to something else.  Then
do it again.  Do it several times.  After some indeterminate number of
repetitions, this task WILL cause Mozilla to crash.

Actual Results:  
It crashes.

Expected Results:  
Not crashing would be nice :)

Dr Watson Sez:
FAULT ->615cb137 394108           cmp     [ecx+0x8],eax         
ds:00a7d5d2=????????

Alas, it was not kind enough to tell me WHICH module was loaded at that address.

However, since I had to restart it to send in this bug report, I used Process
Explorer (I love sysinternals!) to view the process, and it appears to have been
a death in 'gtklayout.dll'.

If I had a COFF .dbg file for this DLL, I could probably provide a LOT more
useful information, since the thing is HUGE.


I am marking the Severity as 'Normal' because, while it is a bug that causes
crashing, it's not likely that most people will encounter it.

Comment 1

[Stevie-O]

Attachment: Dr Watson output from crash

If someone could supply COFF .dbg files for the Mozilla DLLs, the stack traces
would become MUCH more useful.

Comment 2

[Boris Zbarsky [:bzbarsky]]

*** This bug has been marked as a duplicate of 111411 ***