User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 Build ID: 20111008085652 Steps to reproduce: I was typing a long email, then Thunderbird crashed. FML. Actual results: Thunderbird Crashed. Don't know why. The computer was asleep before, and was resumed a while later. This could have to do with the IMAP connecting for the first time after resuming. I started the composition only a few minutes after resuming. There are also several filters, and quite a few emails in the inbox (perhaps a thousand or more) that haven't been filtered yet. Expected results: It shouldn't have crashed.
(In reply to Paul Kenyon from comment #0) Please get a stacktrace of the crash: http://support.mozillamessaging.com/en-US/kb/thunderbird-crashes
I've got the crash ID: 088c9678-b545-4b53-99fa-52e592111120 Is that sufficient? Otherwise, I've installed the debug symbols. I'll start running from a debugger, too, and see if I can reproduce.
Is this the crash report https://crash-stats.mozilla.com/report/index/bp-088c9678-b545-4b53-99fa-52e592111120 ?
Crash Signature: [@ nsCOMPtr_base::~nsCOMPtr_base | nsImapMailCopyState::~nsImapMailCopyState ]
It looks like something to do with the IMAP store, maybe nothing to do with the composition. Maybe storing the draft on the server or fetching new messages in the background. Yes, maybe the connection after resume was in a bad state.
Component: General → Networking: IMAP
Product: Thunderbird → MailNews Core
QA Contact: general → networking.imap
Paul do you also crash when no extensions are running/installed ?
Severity: normal → critical
Status: UNCONFIRMED → NEW
Ever confirmed: true
Paul? same issue as bug 610995?
I don't really know Wayne, but I think it may be the same bug - maybe the problem is in nsImapMailCopyState, in the Release function? I think the fact that I was composing a message was a coincidence, because it never happened for me since then, but I've had many other crashes after resume from sleep. I have disabled all extensions since then, and have been running without. It still crashes all the time after resume.
I wish I you could just view the list of my submitted crash reports. Here are my three most recent, so you can get an idea of how different each report is. The common link with all of these is that it happens after resuming the system. https://crash-stats.mozilla.com/report/index/bp-55ec1b61-b221-419c-a2f5-a36982120124 https://crash-stats.mozilla.com/report/index/bp-ca154f11-0595-419c-a6e0-467fb2120123 https://crash-stats.mozilla.com/report/index/bp-b5f6c437-92b7-494e-98e2-8e7352120121
you seem to be suffering the same crash-signature-itus that another linux user has been experiencing ludo, do you remember which bug that is?
(In reply to Wayne Mery (:wsmwk) from comment #9) > ludo, do you remember which bug that is? No. And it doesn't ring a bell to me.
Christian is the other person with wandering crash sigs
(In reply to Paul Kenyon from comment #8) > I wish I you could just view the list of my submitted crash reports. Here > are my three most recent, so you can get an idea of how different each > report is. Paul, does this reproduce if you are using Thunderbird started in safe mode? Paul's crash sigs were clearHashEntry XPCConvert::JSObject2NativeInterface ReleaseObjects
(In reply to Wayne Mery (:wsmwk) from comment #12) > Paul, does this reproduce if you are using Thunderbird started in safe mode? > > Paul's crash sigs were > clearHashEntry > XPCConvert::JSObject2NativeInterface > ReleaseObjects Wayne, I'm actually not experiencing crashes anymore. I've made a few changes since then: * Running new versions of Thunderbird (worked my way up to 12.0.1) * Running Sieve instead of thunderbird filters * The new versions have Conversations plugin installed and running. Not sure if this stuff matters for much. Thunderbird was still "freaking out" with the other two changes before using Sieve server-side filters. When downloading mail, it would go to 100% CPU, then operate very very slowly when loading messages. The workaround was just to exit and restart. I'm okay with this ticket being closed now, since I can't reproduce and don't really have many more details to provide.
*Thanks* for the update. I'll opt for incomplete, since we never quite had a handle on the cause.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.