Closed Bug 1679324 Opened 4 years ago Closed 3 years ago

78.5.0 periodically hangs up with very high CPU utilization for 10 - 20 seconds

Categories

(Thunderbird :: Mail Window Front End, defect)

defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: bob_gilman, Unassigned)

References

Details

(Keywords: perf)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:83.0) Gecko/20100101 Firefox/83.0

Steps to reproduce:

Don't know how to reproduce - it just seems to happen periodically.

Actual results:

When working in some other window, I go to compose an email or check for an email, and I find I cannot select a different email, nor can I move the slider on the currently-selected email - Thunderbird appears locked up and Task Manager indicates very high CPU usage. The problem clears after 10-20 seconds.

Expected results:

Thunderbird should have responded right away.

This just happened while I was reading email. The CPU utilization ran around 33% for about 45 seconds, then fell and Thunderbird responded normally.

The two most likely possibilities

  • specific to version 78 - hardware acceleration: options > type in "accel" > uncheck use hardware acceleration > restart
  • for any thunderbird update - antivirus software: test by starting Windows in safe mode
Keywords: perf
See Also: → 683651

I still see the problem after unchecking "hardware acceleration" in the options. I've tried running an antivirus scan (MalwareBytes), then trying to get messages: that seemed to block Thunderbird, but when I tried it again, it did not. I did note that I was able to refresh a webpage quickly while Thunderbird was unresponsive and running at ~33% CPU utilization. It doesn't appear that internet access is running slow.

Did you try windows started in safe mode?

Flags: needinfo?(bob_gilman)
Whiteboard: [closeme 2021-07-10]
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Flags: needinfo?(bob_gilman)
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2021-07-10]
You need to log in before you can comment on or make changes to this bug.