Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

Excessive CPU usage after upgrading to 102.3.1 (32-bit) on Windows 10

more options

Thunderbird automatically upgraded to version 102.3.1 (32-bit) this morning when my Windows 10 computer restarted after a Windows Update. Since then, Task Manager shows thunderbird.exe to be consistently using 5-10% of the CPU. If I go to offline mode, the usage goes to 0. This is new behavior after the upgrade. Any suggestions for fixing that would be appreciated.

Thunderbird automatically upgraded to version 102.3.1 (32-bit) this morning when my Windows 10 computer restarted after a Windows Update. Since then, Task Manager shows thunderbird.exe to be consistently using 5-10% of the CPU. If I go to offline mode, the usage goes to 0. This is new behavior after the upgrade. Any suggestions for fixing that would be appreciated.

Gekose oplossing

The problem seems to have resolved itself after a couple of hours; performance is back to normal again. I'm guessing it must have been doing some kind of start-up maintenance, like indexing my existing email database or some such. I don't know if that's normal with an upgrade or not, as I don't normally look at the task manager right after a Thunderbird upgrade; I just knew that it was different from the normal steady-state performance I had previously been seeing.

Lees dié antwoord in konteks 👍 0

All Replies (1)

more options

Gekose oplossing

The problem seems to have resolved itself after a couple of hours; performance is back to normal again. I'm guessing it must have been doing some kind of start-up maintenance, like indexing my existing email database or some such. I don't know if that's normal with an upgrade or not, as I don't normally look at the task manager right after a Thunderbird upgrade; I just knew that it was different from the normal steady-state performance I had previously been seeing.