GNOME Bugzilla – Bug 423323
[blocked] Thunderbird 3.0-a1 crashes every time I close a message.
Last modified: 2008-07-22 19:27:01 UTC
Steps to reproduce: 1. Start Thunderbird 2. Open a message 3. Close the message. Stack trace: Other information:
Confirmed with Thunderbird build from trunk this morning. I've filed Mozilla bug #375698 on this. https://bugzilla.mozilla.org/show_bug.cgi?id=375698 Thanks for reporting it.
Back in late March, early April Thunderbird was remarkably unstable and I used to see this issue. While plenty of Thunderbird issues still exist, this does not seem to be one of them. :-) Hermann and Rich, can you still reproduce this?
Tried it on 15th May. Yes, I can still reproduce it.
Drat! :-( Since I cannot reproduce it, could you please do me a super big favor and enable talkback, crash thunderbird, and get me the tb number so that I can add the contents from it to the existing mozilla bug? That usually gets their attention faster than gdb output. Dunno why.... Thanks much in advance!
It gives me a nice option to attach to the debugger, so I did that. Here's the stack trace for just clicking on a mail message in the message header list. Note that this is without Orca running but with accessibility enabled. This is on my Ubuntu Feisty 32 bit system with Thunderbird 3.0alpha built from a checkout from 14th May. (gdb) where
+ Trace 135888
I'll now try starting Orca first and see if I can actually reproduce the original bug submitted.
Nope. I get the same crash even with Orca running. I'm unable to get to the point where I can try to reproduce the steps in the initial description.
Hmmm.... I didn't build Thunderbird. I just grab the latest nightly's. I wonder if that makes a difference....
Last time I looked I didn't see a Thunderbird nightly. Where should I be looking? I'll try that tomorrow.
ftp://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-trunk If you just look in nightly, you can find two or three month's worth. Thanks for doing this!!
Using the thunderbird 3.0a1 nightly build from 25th May, I cannot reproduce this problem anymore. Closing as FIXED. I've closed the Mozilla bug too. Thanks Joanie.