Thunderbird:Testing:Shutdown Hang: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (add firewall software)
(revamp)
Line 1: Line 1:
A shutdown hang is where Thunderbird is still running after you shut it down using exit or some other method. There are many causes for hangs. To determine why Thunderbird is hung, broadly speaking it is helpful to
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.  
* '''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 =


'''describing the environment''' - When describing the environment of your hang, the answers to these easy questions helps identify the type of hang:
So it is helpful to
# 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 by disabling add-ons until you find the add-on causing the problem, and contact the add-on author.
* '''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 [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, 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}})
#* does hang happen without calendar/lightning extension? ({{Bug|532435}})
# what firewall software do you run, if any?
# What firewall software do you run, if any? Does it hang with firewall disabled?
# cpu usage - is usage high (pegged), zero, low, or other?
# 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?
# 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)
# Is gloda indexing enabled or disabled? (Tools|Options|Advanced|General)
# are your mail accounts pop, imap, or a combination?
# Are your mail accounts pop, imap, or a combination?
# did the computer go into sleep or hibernate while Thunderbird was running?
# 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?
# 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


'''stacktrace''' - If you can, please :
'''Obtain a stacktrace''' - If you can, please :
* create get a stacktrace using _hang_ instructions in these references and attach stacktrace file to [https://bugzilla.mozilla.org/enter_bug.cgi?product=Thunderbird a bug]:
* Get a stacktrace using _'''hang'''_ instructions in these references.  The stacktrace file can then be attached to 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]
** [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]]
** [[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 to reproduce''' - If you are able, please try to determine if there is a list of steps (1. first step, 2. second step, ...) which reliably causes the hang.
'''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 [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
* '''open bugs - see "shutdown hang" query at [[Thunderbird:Bug_Queries]].'''
<!-- 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|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]
** {{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}} comment 12
References:
** {{bug|504971}} comment 15
* {{bug|504971}} see comment 12
* {{bug|504971}} see comment 15


Fixed bugs in version 3 (most recent at top):  
Fixed bugs in version 3 (most recent at top):  
* {{bug|494014}} shutdown hang, high cpu, no open imap connections
* <strike>{{bug|494014}}</strike> shutdown hang, high cpu, no open imap connections
* {{Bug|497598}} hang on shutdown appending msg to imap folder via a filter
* <strike>{{Bug|497598}}</strike> hang on shutdown appending msg to imap folder via a filter
* {{Bug|487965}} hang on shutdown with open imap connections and zero cpu
* <strike>{{Bug|487965}}</strike> hang on shutdown with open imap connections and zero cpu
* {{Bug|420744}} Shutdown fails with 100% cpu load when auto-complete over LDAP  
* <strike>{{Bug|420744}}</strike> 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)
* <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)
* {{Bug|516388}} Hang when exiting Archives smart folder is used
* <strike>{{Bug|516388}}</strike> 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
* <strike>{{Bug|497059}}</strike> Hang with unreliable wifi connection, either when re-connecting to email server, or on shutdown


Hangs caused by other software
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|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

Revision as of 18:37, 17 June 2010

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:

  1. Operating system, version, and Thunderbird version
  2. 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)
  3. What firewall software do you run, if any? Does it hang with firewall disabled?
  4. Cpu usage - is usage high (pegged), zero, low, or other?
  5. 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?
  6. Is gloda indexing enabled or disabled? (Tools|Options|Advanced|General)
  7. Are your mail accounts pop, imap, or a combination?
  8. Did the computer go into sleep or hibernate while Thunderbird was running?
  9. Was online or offline used, either via your explicit action, or automatically due to a dropped network connection?
  10. 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 :

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:

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

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