Changes

Jump to: navigation, search

Thunderbird:Testing:Shutdown Hang

943 bytes added, 18:37, 17 June 2010
revamp
A shutdown hang is where If you close, shut down or exit Thunderbird and it is still running after , then you shut it down using exit or some other methodhave a shutdown hang. There But you shouldn't just report with no additional information, because there are many causes and symptoms for hangs. To determine why Thunderbird is hung, broadly speaking it is helpful to * '''describe the environment''' (described below) * '''obtain a stacktrace''' (described below)* determine a list of '''steps to reproduce''' - which may require some experimentation testing on your part
You might not be able to do everything requested here, but it is important to provide as much of the needed information as you can, and state how often you see the hang (always, rarely, etc). = Symptoms =
So it is helpful to * '''describing describe the environment''' - When describing * '''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 environment of your hang(always, rarely, etc).  '''Describe the answers to environment''' - Answers these easy questions helps identify the type of hangshould be stated in a bug report to describe your environment:# Operating system, version, and Thunderbird version# Does the hang happen with Thunderbird started in [https://support.mozillamessaging.com/en-US/kb/Safe+Mode safe mode]? If it can't be reproduced in safe mode then the problem could be an extension. Experiment , and you will want to experiment by disabling add-ons until you find the add-on causing the problem, and then contact the add-on author.
#* does hang happen without calendar/lightning extension? ({{Bug|532435}})
# what What firewall software do you run, if any? Does it hang with firewall disabled?# cpu 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 Is gloda indexing enabled or disabled? (Tools|Options|Advanced|General)# are Are your mail accounts pop, imap, or a combination?# did Did the computer go into sleep or hibernate while Thunderbird was running?# was 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 [[MailNews:Logging|imap:5 log]] in a log file, which can be attached to a bug report
'''Obtain a stacktrace''' - If you can, please :* create get Get a stacktrace using _hang_ _'''hang'''_ instructions in these references and attach . The stacktrace file can then be attached to [https://bugzilla.mozilla.org/enter_bug.cgi?product=Thunderbird a bug]:report.
** [https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report How_to_get_a_stacktrace_for_a_bug_report]
** [[Thunderbird:Testing:Get_A_Debug_Thunderbird_Hang_Stack]]
* attach [[MailNews:Logging]] imap log file to bug, if imap connections are shown in the netstat results above
'''steps Steps to reproduce''' - If you are able, please try to Please determine if there is a list of steps (1. first step, 2. second step, ...) which reliably causes 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 [https://bugzilla.mozilla.org/enter_bug.cgi?product=Thunderbird file a bug] and include all the information obtained in the steps above.
Related bugs[http: * '''//bit.ly/bUY5HM Bugzilla query of open , invalid and fixed bugs ] from the beginning of time<!-- see "shutdown hang" query at [[Thunderbird:Bug_Queries]].'''--> 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]* referencesReferences:** {{bug|504971}} see comment 12** {{bug|504971}} see comment 15
Fixed bugs in version 3 (most recent at top):
* <strike>{{bug|494014}} </strike> shutdown hang, high cpu, no open imap connections* <strike>{{Bug|497598}} </strike> hang on shutdown appending msg to imap folder via a filter* <strike>{{Bug|487965}} </strike> hang on shutdown with open imap connections and zero cpu* <strike>{{Bug|420744}} </strike> Shutdown fails with 100% cpu load when auto-complete over LDAP * <strike>{{Bug|495551}} </strike> 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)* <strike>{{Bug|516388}} </strike> Hang when exiting Archives smart folder is used* <strike>{{Bug|497059}} </strike> Hang 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
Canmove, confirm
2,079
edits

Navigation menu