Thunderbird throbber spins all the time, consuming large amount of cpu time
Thunderbird version 102.3.1 (32-bit), Windows 10 (up to date). 4 core 64-bit system, 16GB of memory.
Intermittently, Thunderbird (TB) will start consuming an entire core of my 4 core system, or 25% of cpu time. While this is happening, the throbber (the spinner on the mail toolbar between the "tag" and "add a task" icons) spins continuously. While this happening, the system is sluggish.
I've seen other reports where the suggestions are:
- compact all folder (done) - remove all the .msf files in the profile (done)
It has gotten to the point where I don't only run TB once or twice a day to download mail and check the calendar.
Any other suggestions or tips, or any other information that I can supply to help resolve this issue?
Thank!
Chosen solution
Hi Matt,
I was not aware of the activity manager until now - thanks for pointing it out. At first glance, it appears that TB was trying to sync with Google Calendar. After disabling all the google calendar entries on TB and restarting, the cpu load is now only when I'm actively doing something in the mail system. So, it appears right now that the calendar sync issue may have the issue. But, as previously mentioned, this is an intermittent issue, I'm going to wait a day or so before declaring this solved.
thanks for the reply and for the help!
Read this answer in context 👍 0All Replies (2)
Have you tried leaving the activity manager open to see what Thunderbird thinks it is doing? Like getting mail or indexing
What appears in the error console (ctrl+Shift+J) while this is happening?
Chosen Solution
Hi Matt,
I was not aware of the activity manager until now - thanks for pointing it out. At first glance, it appears that TB was trying to sync with Google Calendar. After disabling all the google calendar entries on TB and restarting, the cpu load is now only when I'm actively doing something in the mail system. So, it appears right now that the calendar sync issue may have the issue. But, as previously mentioned, this is an intermittent issue, I'm going to wait a day or so before declaring this solved.
thanks for the reply and for the help!