Closed Bug 1739178 Opened 3 years ago Closed 3 years ago

100% CPU in idle with language packs

Categories

(Thunderbird :: General, defect)

Thunderbird 91
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1728744

People

(Reporter: bill.murray, Unassigned)

References

Details

(Keywords: dupeme, perf)

User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:94.0) Gecko/20100101 Firefox/94.0

Steps to reproduce:

Open thunderbird. Setup 2 imap accounts (~10K messages in inbox and folders) and lightning with ~20 ics calendars on 30minute refresh.

Actual results:

CPU usage however at 100% (1 core) permanently. Actually it has been like this for many months. I have however added a profiling: https://share.firefox.dev/3bDswTy which perhaps helps someone understand this.

Expected results:

Some idle state, battery not drained.

Component: Untriaged → General
Keywords: perf
Product: Thunderbird → Calendar
Summary: Excessive CPU in idle → 100% CPU in idle

Do you have a lang pack installed? Tried Help | Troubleshoot mode?

Hi Magnus,
Thanks for the response. I don't know what you are driving at with langpacks, but here are the rpms:
langpacks-core-font-en-3.0-15.fc35.noarch
gawk-all-langpacks-5.1.0-4.fc35.x86_64
glibc-all-langpacks-2.34-7.fc35.x86_64
glibc-langpack-en-2.34-7.fc35.x86_64
langpacks-core-en-3.0-15.fc35.noarch
langpacks-core-en_GB-3.0-15.fc35.noarch
libreoffice-langpack-en-7.2.2.2-1.fc35.x86_64
langpacks-en-3.0-15.fc35.noarch
evolution-data-server-langpacks-3.42.0-1.fc35.noarch
evolution-langpacks-3.42.0-1.fc35.noarch
evolution-ews-langpacks-3.42.0-1.fc35.noarch
langpacks-en_GB-3.0-15.fc35.noarch

troubleshoot mode I was also unaware of. Awesome! It cures the problem! So this means I should be looking at my add-ons? I have Mail merge, mailbox alert, provider for exchange activesync, provider for google calendar, & tbsync. But when I restart thunderbird in normal mode...the CPU burn is gone!!!! So it seems a quick trip into troubleshoot and back out has cured a long-standing issue. While this is great I cannot help feeling that a reproducible issue would be easier to eliminate...
But thanks!!!

I think magnus has nailed it. THere is currently a problem with language packs. You might disable them until the problem is solved

Blocks: tb91found
Keywords: dupeme
Product: Calendar → Thunderbird
Summary: 100% CPU in idle → 100% CPU in idle with language packs

Hi Magnus,
Thanks...if the CPU usage climbs again I'll try. A quick google seemed to suggest I need to remove the rpms, there is no disable in thunderbird?
Bill

The official thunderbird builds do not ship any language packs, and installed lang-packs can then be disabled like normal add-ons.
But for distro-installed ones I don't know...

Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE

Hi Magnus,
After leaving the computer overnight the power usage of thunderbird climbed up to 100% again. So I tried removing the rpms langpacks-core-en_GB-3.0-15.fc35.noarch langpacks-en_GB-3.0-15.fc35.noarch and cycling thunderbird through troubleshoot mode again. This fixed things for a couple of hours, but now I am back to 100% CPU usage. I am reluctant to delete the langpacks-en-3.0-15.fc35.noarch - would that mean I had no languages?
This does not feel to me like a duplicate of 1728744 - startup is fast.
Does the profiling not provide any clues? The time is going in "pulltimelinedata" - is that part of lightning?

(In reply to Bill Murray from comment #6)

Hi Magnus,
After leaving the computer overnight the power usage of thunderbird climbed up to 100% again. So I tried removing the rpms langpacks-core-en_GB-3.0-15.fc35.noarch langpacks-en_GB-3.0-15.fc35.noarch and cycling thunderbird through troubleshoot mode again. This fixed things for a couple of hours, but now I am back to 100% CPU usage. I am reluctant to delete the langpacks-en-3.0-15.fc35.noarch - would that mean I had no languages?
This does not feel to me like a duplicate of 1728744 - startup is fast.

Your problem is covered in bug 1728744. bug 1728744 has more symptoms than are listed in the title.

You need to log in before you can comment on or make changes to this bug.