Thunderbird crashed while leaving it running overnight



14 years ago
13 years ago


(Reporter: Adam Petaccia, Assigned: Scott MacGregor)



Firefox Tracking Flags

(Not tracked)




14 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040701 Firefox/0.9.1
Build Identifier: Thunderbird version 0.7.1 (20040701)

I don't know what caused it to crash, but when I came back in the morning I saw
"core dumped" in the terminal, and thunderbird quit.  Obtaining a bt showed this:

#0  0xffffe410 in ?? ()
(gdb) bt
#0  0xffffe410 in ?? ()
#1  0xbfffea6c in ?? ()
#2  0x0000000b in ?? ()
#3  0x00001581 in ?? ()
#4  0x47f8c351 in raise () from /lib/
#5  0x08056bad in nsProfileLock::FatalSignalHandler ()
#6  <signal handler called>
#7  0x08df7c57 in ?? ()
#8  0x402c1ec6 in ?? ()
   from /usr/lib/MozillaThunderbird/components/
#9  0x08df7c5c in ?? ()
#10 0x00000003 in ?? ()
#11 0x00000001 in ?? ()
#12 0x40012573 in JS_free () from /usr/lib/MozillaThunderbird/
#13 0x41362d81 in nsJSContext::FireGCTimer ()
   from /usr/lib/MozillaThunderbird/components/
#14 0x4003a240 in js_GC () from /usr/lib/MozillaThunderbird/
#15 0x4003985c in js_ForceGC () from /usr/lib/MozillaThunderbird/
#16 0x40012a9e in JS_GC () from /usr/lib/MozillaThunderbird/
#17 0x4139679f in non-virtual thunk to nsDOMScriptObjectFactory::Release() ()
   from /usr/lib/MozillaThunderbird/components/
#18 0x08672338 in ?? ()
#19 0xbfffef9c in ?? ()
---Type <return> to continue, or q <return> to quit---
#20 0x4141fb08 in nsIGeneratedContentIterator::GetIID()::iid ()
   from /usr/lib/MozillaThunderbird/components/
#21 0x40143593 in nsCOMPtr_base::assign_from_qi ()
   from /usr/lib/MozillaThunderbird/
#22 0x400dc4e9 in nsObserverService::GetObserverList ()
   from /usr/lib/MozillaThunderbird/
#23 0x400d2a35 in NS_ShutdownXPCOM ()
   from /usr/lib/MozillaThunderbird/
#24 0x0804eb82 in ScopedXPCOMStartup::~ScopedXPCOMStartup ()
#25 0x0805184b in xre_main ()
#26 0x0804c843 in main ()

Reproducible: Didn't try
Steps to Reproduce:

Comment 1

14 years ago
Could you try to reproduce and provide TalkBack incident ID?
Severity: normal → critical
Keywords: crash

Comment 2

14 years ago
reporter: the stack seem to indicate the app was trying to quit...

Comment 3

14 years ago
erm, forget that, we need a real stack trace, getiid should be a terminal node,
showing up in the stack trace as it does means the stack isn't useful to us
mortals (and i sometimes can tolerate bogus stacks).

Comment 4

14 years ago
I'm sorry, but I no longer use mozilla-thunderbird (not related to this bug). 
I've switched to ximian's evolution.  I can no longer test this bug.

Comment 5

14 years ago
I have had crashes when I haven't been interacting with Thunderbird on my work
machine for a long time. It seems to be more of a problem when my SSH connection
back home dies (which I tunnel my mail over), but if I just kill my SSH
connection it doesn't seem to bother Thunderbird. Perhaps it is when the work
connection goes down, killing my SSH connection that does it. I suppose it
depends on if PuTTY does anything different on a user invoked quit to a forced
bail out.

It has happened over night and a couple of times yesterday with 1.0, but
unusually I didn't have the opportunity to send any talkback. I will switch back
to a build from a couple of days ago and see if I can come up with anything if
you like.

This is on Windows XP FYI.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.