1202110 - TB uses 100% of a CPU

Status: RESOLVED DUPLICATE of bug 855751

(Thunderbird :: Untriaged, defect)

Description

[Jim Moe]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:40.0) Gecko/20100101 Firefox/40.0
Build ID: 2015080700

Steps to reproduce:

Used Thubderbird


Actual results:

At some point TB start using 100% of a CPU, usually within 2 - 3 days after startup. TB is basically unstable at this point although most functions are more or less available. Quitting is not one of them; TB must be Force Quit.

This puts the user in a ridiculous bind. Because of issue #855751 it is most desirable to keep TB running, not Quit each day. Yet TB must now be Force Quit every 1 or 2 days.


Expected results:

TB should continue operating like it does immediately after startup.

Comment 1

[Jim Moe]

Also: This is a fairly recent issue. It started about v34, maybe v35?

Comment 2

[:aceman]

You were using the betas or nightlies? The previous official stable release before 38 was 31.

Maybe you would be able to get a performance profile of TB using https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Reporting_a_Thunderbird_Performance_Problem_with_G .

Comment 3

[Jim Moe]

Ah, no. I was not paying attention to the version numbers and assumed a monotonically increasing value. The issue has presented itself in whatever version number the most recent two or three releases are.

Comment 4

[Wayne Mery (:wsmwk)]

(In reply to Jim Moe from comment #3)
> Ah, no. I was not paying attention to the version numbers and assumed a
> monotonically increasing value. The issue has presented itself in whatever
> version number the most recent two or three releases are.

Thunderbird version and release observe FIrefox *ESR* numbering. See 
 https://www.mozilla.org/en-US/firefox/organizations/faq/
 https://wiki.mozilla.org/Enterprise/Firefox/ExtendedSupport:Proposal

A more accurate time frame please, since you don't know which releases were affected. Two versions would be roughly two years. Two releases would be roughly 12 weeks, but as aceman indicates potentially encompasses both version 31 and 38.


>  most functions are more or less available. Quitting is not one of them; TB must be Force Quit.
What functions for example still work?
What happens when you attempt quit?

> Because of issue #855751 it is most desirable to keep TB running, 
does this mean bug 855751 occurs mostly or entirely for you on startup?

Comment 5

[Jim Moe]

Part of the reason for the fuzziness is that I am not the user of the OS/X-based TB. The user does not necessarily tell me when there are problems, or all of the details of them, or when they arise.

The 100% CPU issue is fairly recent, AFAIK, let's say within the last two releases (not versions).

The non-functionality: The speller tags all words as misspelled, sometimes a new message cannot be created. (I have not had the opportunity to explore the lack of functions.)

Using Quit: Nothing happens; the request is ignored. Hence the need for Force Quit.

Relationship to bug 855751: Yes, that major defect is a startup problem. The OS/X build of TB does not seem to keep a local copy of the account folders; I see them added as TB queries the server every time TB is started. Because of the continuous loss of preferences and tagging, it is desirable to restart TB as rarely as possible. With this new problem, 100% CPU, the user is forced to restart TB.

Comment 6

[Wayne Mery (:wsmwk)]

I suggest this is a manifestation of bug 855751, and focus efforts there. If the problem continues after that is resolved then we should reopen this bug