Thunderbird:Testing:Shutdown Hang
If you close, shut down or exit Thunderbird and it is still running, then you have a shutdown hang. But you shouldn't just report with no additional information, because there are many causes and symptoms for hangs.
Symptoms
So it is helpful to
- describe the environment
- obtain a stacktrace
- determine steps to reproduce, a sequence of steps that occur before you shut down
It is important that you provide as much of information as possible, and state how often you see the hang (always, rarely, etc).
Describe the environment - Answers these easy questions should be stated in a bug report to describe your environment:
- Operating system, version, and Thunderbird version
- Does the hang happen with Thunderbird started in safe mode? If it can't be reproduced in safe mode then the problem could be an extension, and you will want to experiment by disabling add-ons until you find the add-on causing the problem, then contact the add-on author.
- does hang happen without calendar/lightning extension? (bug 532435)
- What firewall software do you run, if any? Does it hang with firewall disabled?
- Cpu usage - is usage high (pegged), zero, low, or other?
- run netstat -a -b -o | grep -i thunderbird (in MS-Windows in a dos command window do netstat -a -b -o) - are connections shown from thunderbird to ldap, imap mail server, or other protocols?
- Is gloda indexing enabled or disabled? (Tools|Options|Advanced|General)
- Are your mail accounts pop, imap, or a combination?
- Did the computer go into sleep or hibernate while Thunderbird was running?
- Was online or offline used, either via your explicit action, or automatically due to a dropped network connection?
- If imap connections are shown in the netstat results above and if needed by the devoloper, get an imap:5 log in a log file, which can be attached to a bug report
Obtain a stacktrace - If you can, please :
- Get a stacktrace using _hang_ instructions in these references. The stacktrace file can then be attached to a bug report.
Steps to reproduce - Please determine if there is a list of steps (1. first step, 2. second step, ...) which seem to cause the hang. This would be things you see and a sequence of steps that occur before you shut down. Often there isn't a single set of steps or a set of steps that cause the hang every time. So you may need to experiment and test to determine steps. Because it is not always possible to determine steps, it is important is that you at least have all the other details listed above.
Bugs
Filing a bug : If none of the bugs mentioned below fit your symptoms, please file a bug and include all the information obtained in the steps above.
Bugzilla query of open, invalid and fixed bugs from the beginning of time
Open bugs
- see bugzilla query above
- selected list of open bugs
- bug 479373 Hang on shutdown if there are outstanding SSL requests
- bug 508263 3.0b3 hangs on exit/shutdown with high cpu, no imap connections [Mac only?] [speculation: losing the network connection/sleeping]
References:
- bug 504971 see comment 12
- bug 504971 see comment 15
Fixed bugs in version 3 (most recent at top):
bug 494014shutdown hang, high cpu, no open imap connectionsbug 497598hang on shutdown appending msg to imap folder via a filterbug 487965hang on shutdown with open imap connections and zero cpubug 420744Shutdown fails with 100% cpu load when auto-complete over LDAPbug 495551hang on shutdown, zero cpu, few (1-2) imap connections - from imap url initiated during shutdown (modal alert from imap thread / proxy call to UI thread)bug 516388Hang when exiting Archives smart folder is usedbug 497059Hang with unreliable wifi connection, either when re-connecting to email server, or on shutdown
Hangs caused by other software
- bug 532435 Thunderbird 3.0RC 2 does not quit, high cpu, no imap connection and must be killed - with enigmail error [caused by Engimail]
- and see INVALID bugs in the bugzilla query above