To be most helpful, you will want to
* '''describe your environment''' (including things which includes steps which may help you avoid the problem)* '''determine steps to reproduce''', a sequence of steps you did '''before''' you shut down
* '''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 Questions to answer in a bug report or in a [http://getsatisfaction.com/mozilla_messaging/topics/new posting to support]:
# Does Thunderbird hang ... :
#* when started in [https://support.mozillamessaging.com/en-US/kb/Safe+Mode safe mode]? If it doesn't hang in safe mode you will want to then 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 [[Thunderbird:Testing:Antivirus_Related_Performance_Issues|firewall or antivirus software]] disabled? If it does not, hang goes away then the problem is with that software, not Thunderbird.<small>see [[Thunderbird:Testing:Antivirus_Related_Performance_Issues|firewall or antivirus software]]</small>
# Is gloda indexing enabled or disabled? (Tools|Options|Advanced|General)
# Are your mail accounts pop, imap, or a combination?
# How often you see the hang (always, rarely, etc)?
# CPU usage - is usage zero, low, high (maxed or pegged), or other?
# ldap address book - do you have an ldap directory address book defined?# run netstat - any thunderbird connections to ldap, imap mail server, or other protocolsshown in the netstat display?#* MS-Windows: in open a dos command window(Start, Programs, Accessories, Command Prompt), do '''netstat -a -b -o'''
#* linux/Mac: do netstat -tp | grep -i thunderbird
# If imap connections are shown in the netstat results above and if needed by the devoloper, get an [[MailNews:Logging|imap:5 log]] in a log file, which can be attached to a bug report
:# '''Steps to reproduce'''To recap(STR) - Please determine a list of steps which seem to cause the hang. This list is a sequence of actions (1. xxxx, please concisely report: OS & Thunderbird version2. yyyy, frequency3. zzz, safe mode resultsetc) you did just '''before''' you shut down. Plus the things you see. You may need to experiment to find steps that are reliable, cpu, netstat results, indexing on or off, pop or imap account types, sleep/hibernate usage, online/offline usageand eliminate steps which aren't needed to reproduce the problem. If you can't seem to find a unique set of steps, don't let that stop you from checking the bug list below or filing a bug report ... because the environment information you have collected in earlier steps above may be enough to identify the problem. # '''Obtain a hang stacktrace''' - If you canpossible, please get a stacktrace using _'''hang'''_ instructions in these the referencesbelow, then attach text file containing stacktrace file to a bug report. Anywhere you see "Firefox" in the instructions, please substitute "Thunderbird".#* Windows: [https://developer.mozilla.org/en/How_to_get_a_stacktrace_with_WinDbg] and use "'''!analyze -v -hang'''" instead of !analyze -v -f#* Mac: [[Thunderbird:Testing:Get_A_Debug_Thunderbird_Hang_Stack]]#* Linux: [https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report#Alternative_ways_to_get_a_stacktrace] :'''Steps to reproduceTo 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, STR''' - 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 downAnd, 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 stepsif possible, 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 reporthang stack trace.
= Bugs =
