Thunderbird frequently locks up after changing wireless networks



8 years ago
7 years ago


(Reporter: kbrussel, Unassigned)


({hang, regression})

1.9.1 Branch
Mac OS X
hang, regression

Firefox Tracking Flags

(Not tracked)


(Whiteboard: [has stacktrace])


(2 attachments, 1 obsolete attachment)



8 years ago
Starting with Thunderbird 3.0, the app frequently locks up on Mac OS X, apparently after resuming from sleep and awakening on a different wireless network. I have to force quit the app and restart it when this happens. Attached is the force quit report, where the stack trace seems to implicate the Airport Base Station Agent and not Thunderbird; however, I have not seen this behavior with any other application, and it wasn't happening in earlier versions of Thunderbird.

Comment 1

8 years ago
Created attachment 494413 [details]
Force Quit report including stack traces


8 years ago
Severity: normal → critical
Component: Message Reader UI → Networking
Keywords: hang
Product: Thunderbird → MailNews Core
QA Contact: message-reader → networking
Whiteboard: [has stacktrace]
Version: 3.1 → 1.9.2 Branch


8 years ago
Keywords: regression
Version: 1.9.2 Branch → 1.9.1 Branch
Unfortunately, that stack trace is not usable. Wayne, do you have a page on getting good stack traces on hangs?
Whiteboard: [has stacktrace]
(sorry bout that)

see Obtain a hang stacktrace
I'm pretty sure there's been at least one bug filed about this; CCing Gary & Mark, who I seem to recall having been involved...

Comment 5

8 years ago
Created attachment 494675 [details]
Stacktraces from gdb

Here are the stack traces from within gdb of all running threads when the hang occurs. This is with the product, so I don't know whether it contains proper debug symbols. I'm not going to be able to build the product myself so if there is a debug build somewhere please point me to it.
Attachment #494413 - Attachment is obsolete: true

Comment 6

8 years ago
Created attachment 494676 [details]
Stacktraces from gdb upon Command-Q of wedged process

Here are stack traces from the same binary after hitting Command-Q against the wedged process.
I know we've had issues in the past, but I thought they were resolved in the early 3.0 days. Kenneth: exactly which version of Thunderbird are you on (you can get this from Help -> About)?

Comment 8

8 years ago
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv: Gecko/20101027 Thunderbird/3.1.6
(In reply to comment #4)
> I'm pretty sure there's been at least one bug filed about this; CCing Gary &
> Mark, who I seem to recall having been involved...

My issues were resolved back in the 3.0 days as Mark mentioned :)

Comment 11

8 years ago
(In reply to comment #9)
> Kenneth, I don't have any reason to believe your problem is gone, but would you
> be able to test an alpha from
> xref 
> * bug 508263 the classic Mac [speculation: losing the network
> connection/sleeping]
> * bug 284152, not Mac only, and not a v3 regression.

OK, I've installed Miramar 3.3 Alpha 2 and will report any hangs. The hangs were still happening with Thunderbird 3.1.7, though intermittently. Some days Thunderbird would lock up with every sleep/resume cycle on a different network; sometimes it would go for days and several sleep/resume cycles without locking up.

Comment 12

8 years ago
It's still happening with Miramar 3.3 Alpha 2. It happened when I switched from my work to my home network. Same symptom as with Thunderbird 3.1.7: it stopped collecting new mail, locked up upon Cmd-Q, and I had to force quit the app to exit it.
Kenneth, do you still see this when using version 13, or a development build?

Comment 14

7 years ago
I haven't seen the problem with version 13, but I switched away from using an IMAP mail reader as my primary email setup, so haven't been giving Thunderbird heavy use recently.
thanks. please comment and reopen bug if y ou see the problem again.
Last Resolved: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.