Thunderbird:Testing:Shutdown Hang: Difference between revisions
No edit summary |
(→Bugs) |
||
Line 41: | Line 41: | ||
= Bugs = | = Bugs = | ||
Check the bugs below to see which fit your exact situation after you go through the [[#Symptoms|Symptoms]] list above. If none match your symptoms please [https://bugzilla.mozilla.org/enter_bug.cgi?product=Thunderbird file a bug] and include the information gathered above in [[#Symptoms|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. | |||
* [https://bugzilla.mozilla.org/buglist.cgi?keywords=hang&chfieldto=Now&query_format=advanced&chfield=resolution&keywords_type=allwords&chfieldfrom=4m&short_desc=shutdown%20quit%20exit%20close%20closing%20terminat&bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=normal&short_desc_type=anywordssubstr&product=MailNews%20Core&product=Thunderbird Bug's status changed in last 4 months] (but not necessarily fixed) | |||
* '''All hang bugs: [http://bit.ly/bUY5HM Bugzilla query - open, invalid and fixed bugs from the beginning of time]''' | |||
'''All hang bugs: [http://bit.ly/bUY5HM Bugzilla query - open, invalid and fixed bugs from the beginning of time]''' | |||
<!-- see "shutdown hang" query at [[Thunderbird:Bug_Queries]] --> | <!-- see "shutdown hang" query at [[Thunderbird:Bug_Queries]] --> | ||
* '''Open hang bugs:''' In the bugzilla query above click the Status column to show bugs in Status order | |||
'''Open hang bugs:''' | * 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] | ** {{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: | |||
* {{ | * <strike>{{Bug|532435}}</strike> Thunderbird 3.0RC 2 does not quit, high cpu, no imap connection and must be killed - with enigmail error [caused by Engimail] | ||
* {{ | * <strike>{{Bug|479373}}</strike> (Firefox) Hang on shutdown if there are outstanding SSL requests | ||
* and see INVALID bugs in the "All hang bugs" bugzilla query above | |||
Fixed bugs in version 3 (most recent at top): | Fixed bugs in version 3 (most recent at top): | ||
Line 66: | Line 66: | ||
* <strike>{{Bug|516388}}</strike> Hang when exiting Archives smart folder is used | * <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 | * <strike>{{Bug|497059}}</strike> Hang with unreliable wifi connection, either when re-connecting to email server, or on shutdown | ||
Revision as of 12:03, 25 October 2010
If you close, shut down or exit Thunderbird (or Thunderbird stops on its own) and you see the Thunderbird process is still seen 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.
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 you report with data.
Symptoms
To be most helpful, you will want to
- describe your environment
- 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:
- Operating system and version, and Thunderbird version
- How often you see the hang (always, rarely, etc)?
- Does Thunderbird hang when started in safe mode? If it doesn't hang in safe mode then the problem could be an extension, and you will want to experiment by disabling add-ons until you find which add-on is causing the problem, then contact the add-on author.
- does hang happen without calendar/lightning extension? (bug 532435)
- Does Thunderbird hang with firewall or antivirus software disabled? If it does not, then the problem is with that software, not Thunderbird.
- CPU usage - is usage high (maxed or pegged), zero, low, or other?
- 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
- 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
- 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 if there is a list of steps
- 1. first step
- 2. second step
- 3. ...
which seem to cause the hang. This would be the things you see and a sequence of actions you do just before you shut down. You may need to experiment and test to find steps that seem reliable. But if you can't seem to find a unique set of steps, don't let that stop you from looking at the bug list or filing a bug report, because the environment information you have collected from the list above may be sufficient to identify the cause.
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 532435Thunderbird 3.0RC 2 does not quit, high cpu, no imap connection and must be killed - with enigmail error [caused by Engimail]bug 479373(Firefox) Hang on shutdown if there are outstanding SSL requests- and see INVALID bugs in the "All hang bugs" bugzilla query above
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