185901 - crash on exit

Status: RESOLVED WORKSFORME

(Other Applications :: ChatZilla, defect)

Description

[Robert Ginda]

there have been some reports of crash on exit, and there are about a dozen
talkback reports that talk about exiting chatzilla.

I'll attach a few of the talkbacks here.

Comment 1

[Robert Ginda]

Attachment: talkback: PL_DHashTableRawRemove from ~nsGenericElement

Comment 2

[Robert Ginda]

Attachment: anther one in nearly the same spot.

Comment 3

[Robert Ginda]

Attachment: talkback: nsGenericElement::GetOwnerDocument

Comment 4

[Robert Ginda]

Attachment: talkback: nssCertificate_Destroy

Comment 5

[Robert Ginda]

DOM folks, nsGenericElement is near the top on the first three.  Any ideas?

Comment 6

[Matthias Versen [:Matti]]

"nssCertificate_Destroy" is bug 182803

Comment 7

[Spiros Ioannou]

Attachment: debug from BCB5

This started some weeks ago. Nearly every time I exit mozilla (win2k) it
crashes
with the usual windows error "memory could not be read" and entitled: "DDE
Server Window". I choose to debug to get a screenshot of the registers and asm
but I have no idea if this is mozilla code or some dll code. I will create an
attachment.

Comment 8

[Daniel Yanez]

I have same crash as comment # 7, different builds, different pages (one time,
no page at all). Win2k SP3.

TalkBack:
         TB15500266E
         TB15502680E
         TB15620403M

Comment 9

[Mike Stockman]

A bunch of those talkbacks are probably mine (for weeks with the latest
nightlies, currently 2003010904), so I'm cc'ing myself on this.

If it's helpful to know this, no profile corruption appears to be involved,
since I've tried creating a new one.

Temporary workaround is to leave the Manage Bookmarks window open (ctrl-B) all
of the time. The crash only occurs for me when the last Mozilla window is closed.

Comment 10

[Joergen Ramskov]

I'm on WinXP and Mozilla (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.3.1) Gecko/20030425) crashes consistenly each time I close it. This install
has been upgraded with each new release (uninstall current installed release, 
install new release).

The "crash agent" doesn't seem to get much data on the crash, but WinXP do, I'll
make two attachments with some info.

Comment 11

[Joergen Ramskov]

Attachment: Screenshot of WinXP crash data

One of the two attachments I mentioned in my comment

Comment 12

[Joergen Ramskov]

Attachment: The text file the WinXP crash data (see the screenshot) refers to

Comment 13

[Lapo Luchini]

Some more from me (Mozilla 1.4b Build Id 2003052608 on WinXP):
TB21229611Q
TB20912966X
TB20870012E
TB20750929E
TB20688808K

BTW: I usually Mozilla until it grows "too big" (e.g. 500Mb) and then close
it... and had this bug since a long time.

Comment 14

[Lapo Luchini]

This one is very fresh and could be important as I actually used Mozilla only to
write this very comment #13, time since start to exit, circa 5 minutes.

TB21232738G

Comment 15

[Lapo Luchini]

1.4 release:
TB21828366G
TB21635128Y
TB21594272K
TB21306369W
TB21234766E
TB21233034M
TB21232942Z

Comment 16

[Samuel Sieb]

Haven't heard of this happening for quite a while.  It was probably fixed in
mozilla.

Comment 17

[Lapo Luchini]

Whoops, I did lose the URL of this bug and I added some subsequent crash to bug
201230.
I guess they are somewhat related.

Comment 18

[Samuel Sieb]

This bug is about chatzilla causing mozilla to crash on exit.  That other bug
does not involve chatzilla, so it's a different issue.

Comment 19

[Lapo Luchini]

OK, then the TB i pasted here were incorrect, as I seldom (or never) use
chatzilla ^_^

Comment 20

[James Rome]

TB316813Q, TB315174K, TB315167X, TB305965W, TB304837Y, TB304706Q, TB301186K,
TB261772Y, TB247706Q

It crashes every time for me. Build 2004062708 Win 2k. Unfortunately I cannot
update to a more recent build because of the bug that does not display a uid/pwd
screen on password-protected pages.

Comment 21

[:Gijs (he/him)]

Another 8 months later, can anyone still reproduce this bug?

Comment 22

[:Gijs (he/him)]

Nearly two months after my last request for anyone to reproduce this, nothing
has happened - it's been 10 months since the last report of this. Marking WFM,
if anyone can still reproduce then please reopen this bug.