Closed
Bug 531428
Opened 15 years ago
Closed 15 years ago
TB don´t shutdown, high cpu, no ldap, no imap
Categories
(MailNews Core :: Networking: IMAP, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: blueduck, Unassigned)
Details
(Keywords: hang, stackwanted)
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; de; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 FirePHP/0.3
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; de; rv:1.9.1.4pre) Gecko/20090915 Thunderbird/3.0b4
If i quit TB from menu or via Apple+Q, main window disapears but the process still live and produce a high cpu usage.
Reproducible: Always
Steps to Reproduce:
1. Starting TB
2. Close TB after a few minutes
Comment 1•15 years ago
|
||
Can you try to reproduce with Thunderbird 3.0 Release Candidate 1?
http://www.mozillamessaging.com/en-US/thunderbird/early_releases/downloads/
I tried downgrade to beta 4. So I close TB 3.0 RC1 and copy the app into the application folder but an error occured, which said that the operation could not finished because the object libwidget.rsrc is still in use.
Comment 4•15 years ago
|
||
blueduck, beta 4 would not be any better.
do you see any network connections to news, imap server or ldap if you run netstat from terminal window (I'm assuming Mac has this)?
is cpu maxed at 100%
do any of the *open* (status not verified or fixed) hang bugs match for you?
https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=anywordssubstr;field0-0-0=short_desc;field1-0-2=short_desc;type0-0-1=substring;columnlist=bug_severity%2Cbug_status%2Ccomponent%2Cop_sys%2Ctarget_milestone%2Cstatus_whiteboard%2Ckeywords%2Cshort_desc;field0-0-1=keywords;type1-0-1=substring;resolution=FIXED;resolution=INVALID;resolution=DUPLICATE;resolution=---;value1-0-1=hang;type1-0-2=anywords;value1-0-2=hang%20hangs;chfieldto=Now;query_format=advanced;chfieldfrom=2009-01-01;value1-0-0=%20freez%20froz%20hung%20;type0-0-0=anywordssubstr;value0-0-0=shut%20shutdown%20quit%20clos;field1-0-0=short_desc;product=MailNews%20Core;product=Thunderbird;field1-0-1=keywords
Severity: major → critical
Keywords: hang
Summary: TB don´t shutdown correctly → TB don´t shutdown, high cpu
Version: unspecified → 3.0
No imap, no ldap.
CPU is close to 100%
Change reproducible from always to sometimes.
Maybe there is a relationship to the mailindexer. Right after upgrade TB indexing all mails. There are a lot of them, so if he indexing while I closing TB he hangs.
Now, after TB indexed all mails, shutdown works properly
Comment 6•15 years ago
|
||
blueduck, if you use RC1, and turn off indexing, does the shutdown problem go away?
David, Andrew, I thought there was a shutdown bug related to indexing but I'm not seeing it (but didn't look very hard) amongst https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=anywordssubstr;field0-0-0=short_desc;bug_severity=blocker;bug_severity=critical;bug_severity=major;bug_severity=normal;type0-0-0=anywordssubstr;value0-0-0=shut%20hang%20clos;type1-0-1=substring;value1-0-1=search;resolution=---;query_format=advanced;value1-0-0=gloda%20index;field1-0-0=short_desc;product=MailNews%20Core;product=Thunderbird;product=Toolkit;field1-0-1=component
Yes, I use RC1 but i didn´t turn indexing off.
After TB runs one day (and indexed all mails), shut down works well.
I think the reason for hanging while shutdown is because indexing operation was interrupted and produce an error. This is only my thoughts without any look in code or logs.
Comment 8•15 years ago
|
||
mozStorage in all places, although soon not on trunk or 1.9.2, spins an event loop when it is shutting down the async thread to try and let the async thread finish what it is doing. It is impossible to add new async statements to the execution queue while this is happening, but if something ridiculously costly is in the queue, it could certainly draw out shutdown.
So if someone did a global search for "the" and then tried to quit, Thunderbird might go on living for another 30 seconds while the query runs to completion.
We do have the capability to cancel statements on a sqlite3_step level of granularity. Unfortunately, almost any pathologically expensive SQL statement is going to have one extremely long sqlite3_step (which cannot be interrupted) followed by a series of extremely cheap sqlite3_step invocations.
Likely reasons the async thread would be busy for a longish time would be:
- FTS3 segment merges. These are an amortized cost being paid down and we can't control when they happen.
- Commits through their I/O cost. We control when they happen, but when quitting we don't have much choice unless we want to give up all our hard work.
- Messages in ridiculously long threads or where the user has a ridiculous number of copies of the same messages. The indexer's use of GetMesssagesByMessageId will generate this query which can end up with a lot of matches.
- User queries on ridiculously common words.
Comment 9•15 years ago
|
||
(In this case, I'd rule out the commit since that will be I/O dominated.)
Comment 10•15 years ago
|
||
I'm on XP with RC2 on a migrated profile but running in Safe-Mode, and I have the same problem (already had it with RC1).
TB won't shutdown although windows are closed, but process is still there with 50% CPU...at least for 10 minutes (then I had to close it, I'm at work :) )
Annoying bug!
Comment 11•15 years ago
|
||
I think this is an IMAP issue. Everyone experiencing this, do you have IMAP accounts defined?
Comment 12•15 years ago
|
||
I do have IMAP accounts defined here at work, where the issue is occuring.
I have to check at home though, I only have POP there (and I'm not sure I have the issue)
Updated•15 years ago
|
Component: General → Networking: IMAP
Product: Thunderbird → MailNews Core
QA Contact: general → networking.imap
Version: 3.0 → 1.9.1 Branch
Comment 13•15 years ago
|
||
do you have a dictionary installed? ref Bug 533464
klint, you need to get more info to see whether your issue match this.
Summary: TB don´t shutdown, high cpu → TB don´t shutdown, high cpu, no ldap, no imap
Comment 14•15 years ago
|
||
klint? do you have an update? your hangs are on pop-only, correct?
blueduck, are you all pop? or all imap?
please get a stack trace
https://developer.mozilla.org/En/How_to_get_a_stacktrace_for_a_bug_report
Keywords: stackwanted
Whiteboard: closeme 2010-03-12
Comment 15•15 years ago
|
||
Hi Wayne
It seems that the issue with IMAP was corrected with 3.01 :)
I still have seldom hangs with POP at home, but honestly, I have so many extensions that I can't tell whether it's related to core Thunderbird or to an addon (and I really can't use TB daily without these addons, sorry!)
So, bottom line is: it still happens every now and then, on both IMAP and POP, but far more often than before 3.01 . And it may be related to an addon.
Comment 16•15 years ago
|
||
we also need to know if Mac sleep ever happens before you shutdown. If it does, then this may be a dup of bug 508263. If it doesn't then it's likely a dup of one of these. https://bugzilla.mozilla.org/buglist.cgi?type1-0-0=anywordssubstr&keywords=hang&keywords_type=allwords&short_desc=shutdown&field0-0-0=short_desc&bug_severity=critical&resolution=---&classification=Client%20Software&classification=Components&chfieldto=Now&query_format=advanced&chfieldfrom=2y&short_desc_type=allwordssubstr&type0-0-0=nowords&value0-0-0=count%20counts&field1-0-0=short_desc&product=MailNews%20Core&product=Thunderbird
Until more information is available, I'll close this incomplete because we have an abundance of shutdown hang bugs. Note, I think there are no reports of indexing related shutdown problems
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
Whiteboard: closeme 2010-03-12
You need to log in
before you can comment on or make changes to this bug.
Description
•