Thunderbird:Testing:Shutdown Hang

If you close, shut down or exit Thunderbird (or Thunderbird stops on its own) and you see the Thunderbird process is running in MS-Windows task manager (taskmgr) or linux process status (ps), then you have a shutdown hang. Or perhaps you encountered a message that "Thunderbird is already running". The "already running" message can be a symptom that is not related to hangs, so it is essential that you check taskgmgr or ps to find thunderbird there; if you don't see thunderbird listed, then you do not have a hang.

There are several reported Bugs, but please only comment in a bug, or report a new one, using detailed information which you can obtain from the Symptoms list below. In other words, just reporting or commenting that you hang is not useful - please support your report and comments with data.

Symptoms

To be most helpful, you will want to

• describe your environment (which includes steps which may help you avoid the problem)
• obtain a hang stacktrace
• determine steps to reproduce, a sequence of steps that occur before you shut down

Describe the environment - Answer these easy questions in a bug report or posting to support:

1. Does Thunderbird hang ... :
   • when started in safe mode? If it doesn't hang in safe mode you will want to disable add-ons until you find which add-on is causing the problem, then contact the add-on author.
     • happen without calendar/lightning extension? (bug 532435)
     • happen without enigmail extension?
   • with firewall or antivirus software disabled? If it does not, then the problem is with that software, not Thunderbird.
2. Is gloda indexing enabled or disabled? (Tools|Options|Advanced|General)
3. Are your mail accounts pop, imap, or a combination?
4. Did the computer go into sleep or hibernate while Thunderbird was running?
5. Did you change Thunderbird to online or offline status?
6. Did you move your (laptop) computer to a different network?
7. State your operating system and version. State Thunderbird version from Help > About.
8. How often you see the hang (always, rarely, etc)?
9. CPU usage - is usage zero, low, high (maxed or pegged), or other?
10. run netstat - any thunderbird connections to ldap, imap mail server, or other protocols?
    • MS-Windows: in a dos command window, do netstat -a -b -o
    • linux/Mac: do netstat -tp | grep -i thunderbird
11. 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

To recap, please concisely report: OS & Thunderbird version, frequency, safe mode results, cpu, netstat results, indexing on or off, pop or imap account types, sleep/hibernate usage, online/offline usage

Obtain a hang stacktrace - If you can, please get a stacktrace using _hang_ instructions in these references, then attach stacktrace file to a bug report. Anywhere you see "Firefox" in the instructions, please substitute "Thunderbird".

• Windows: [1] and use "!analyze -v -hang" instead of !analyze -v -f
• Mac: Thunderbird:Testing:Get_A_Debug_Thunderbird_Hang_Stack
• Linux: [2]

Steps to reproduce - Please determine a list of steps which seem to cause the hang.

1. first step

2. second step

3. ...

This list is a sequence of actions you do just before you shut down, plus the things you see. You may need to experiment and test to find steps that seem reliable. If you can't seem to find a unique set of steps, don't let that stop you from looking at the bug list (below) or filing a bug report, because the environment information you have collected be may be enough to match with someone else's report.

Bugs

Check the bugs below to see which fit your exact situation after you go through the Symptoms list above. If none match your symptoms please file a bug and include the information gathered above in Symptoms. Bugs typically do not get fixed quickly. So if a bug's status is still open (not marked fixed), then it probably isn't fixed, even if a new release has been issued.

• Bug's status changed in last 4 months (but not necessarily fixed)
• All hang bugs: Bugzilla query - open, invalid and fixed bugs from the beginning of time
• Open hang bugs: In the bugzilla query above click the Status column to show bugs in Status order
• Selected open bugs:
  • 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 about IDLE
  • bug 504971 see comment 15

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]
• bug 544684 Application hang, GUI closed, process not killable from task manager caused by McAfee
• and for more, see INVALID bugs in the "All hang bugs" bugzilla query above

Fixed bugs in version 3 (most recent at top):

• bug 494014 shutdown hang, high cpu, no open imap connections
• bug 497598 hang on shutdown appending msg to imap folder via a filter
• bug 487965 hang on shutdown with open imap connections and zero cpu
• bug 420744 Shutdown fails with 100% cpu load when auto-complete over LDAP
• bug 495551 hang 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 516388 Hang when exiting Archives smart folder is used
• bug 497059 Hang with unreliable wifi connection, either when re-connecting to email server, or on shutdown