Closed Bug 1844842 Opened 2 years ago Closed 1 year ago

thunderbird 115.0.1 takes high cpu loads 100% one core

Categories

(Thunderbird :: General, defect)

Thunderbird 115
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: tschweikle, Unassigned)

Details

(Keywords: perf)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36

Steps to reproduce:

Switch from Thunderbird 112.13.0 102.13.0 to 115.0.1

Actual results:

While Thunderbird 112.13.0 102.13.0 ran without issues Thunderbird 115.0.1 takes 100% of one core and is unresponsive for tenth of minutes. As soon als core occupancy drops beyond 8% Thunderbird is responsive again. But this does not keep. Load increases after about a minute or two and Thunderbird is again unresponsive for tenth of minutes.

Expected results:

Thunderbird staying responsive, even if occupying one core 100% for actions if more than one core is available.
If only one core is available Thunderbird should be able to stay responsive by giving user actions higher priority.

Version 102.13.0 to 115.0.1

Please obtain a performance profile and post the link here. THanks

Component: Untriaged → General
Keywords: perf

I also experience significant performance issues since 115. Every few seconds, TB becomes unresponsive for some seconds. This is a profile recorded during scrolling the message list, but similar behavior occurs when writing an e-mail, e. g.: https://share.firefox.dev/43Vgw8p

Maybe bug #1847137 is related?

Sadly after updating to TB 115.2.0 on windows 10
TB is directly inresponsible to Windows.
I can move the mouse over TB main windows and there is only an "rolling circle"
so I cannot create a "performance profile" , because Tool box is not openable.
I can not close the TB window in a normal way:
If I click on the cosing "x" , than Windows catches a TB crash.

(In reply to Robert Hartmann from comment #5)

If I click on the cosing "x" , than Windows catches a TB crash.

Please post your crashID. Perhaps we get lucky and it is useful

(In reply to Wayne Mery (:wsmwk) from comment #6)

(In reply to Robert Hartmann from comment #5)

If I click on the cosing "x" , than Windows catches a TB crash.

Please post your crashID. Perhaps we get lucky and it is useful

Sadly no crash report can be submitted - the crashreporter programm did not catch the crash
but WS Windows shows "close unresponsible app" and after that I think some VisualStudio Debugger catched
but could not handle the situation.

I will try it on an other machine again.

(In reply to cpohle from comment #3)

I also experience significant performance issues since 115. Every few seconds, TB becomes unresponsive for some seconds. This is a profile recorded during scrolling the message list, but similar behavior occurs when writing an e-mail, e. g.: https://share.firefox.dev/43Vgw8p

Your issue appears to be graphics related. So I have doubts it is related to bug 1847137. Do you still experience this with 115.2.0 ?

Flags: needinfo?(cpohle)

tps ...

(In reply to Wayne Mery (:wsmwk) from comment #2)

Please obtain a performance profile and post the link here. THanks

Flags: needinfo?(tschweikle)

(In reply to Robert Hartmann from comment #5)

Sadly after updating to TB 115.2.0 on windows 10
TB is directly inresponsible to Windows.
I can move the mouse over TB main windows and there is only an "rolling circle"
so I cannot create a "performance profile" , because Tool box is not openable.

Not Responding and hanging sounds like a different bug. Please file a new bug report.

(In reply to Wayne Mery (:wsmwk) from comment #8)

Your issue appears to be graphics related. So I have doubts it is related to bug 1847137. Do you still experience this with 115.2.0 ?

Yes, performance is still significantly worse than with pre-Supernova releases. The sluggish UI is really an UX killer on my aged iMac.

Flags: needinfo?(cpohle)

This issue is not seen any more with windows or linux versions of thunderbird 115.2.0

Flags: needinfo?(tschweikle)

Previous comments - please file new bug reports for issues that are still seen with version 115 or newer, and copy your comments to the new bug.

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.