Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

Avatar for Username

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

I see my exact problem in a supposedly fixed bug report, but it has not been fixed for me

  • 1 valiny
  • 0 manana an'ity olana ity
  • 14 views
  • Valiny farany nomen'i Ed

jenniferehle1
jenniferehle1
more options

Whenever I reopen Thunderbird 140esr (it has this behavior on 140.0, 140.1.0 and now 140.2.0), there is a second lower case "thunderbird" process that causes 50-150% CPU usage in the two processes. Also if I quit with both processes active I get an error message that "thunderbird" has unexpectedly quit. If I quit the "thunderbird" process with Activity Monitor the CPU issues go away for as long as the Thunderbird app is open.

I found this exact issue as a reported bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1977514&_gl=1*1coyjyr*_ga*ODYxNzE0NjQyLjE2OTY0NDU3MDg.*_ga_2VC139B3XV*czE3NTY2OTAwOTckbzMkZzEkdDE3NTY2OTAyMzYkajI0JGwwJGgw It says that it was fixed, though, and it has not been for me. Does that mean it's only been fixed in versions not yet released, or is it already (incorrectly) believed to be fixed for everyone? Thank you.

Whenever I reopen Thunderbird 140esr (it has this behavior on 140.0, 140.1.0 and now 140.2.0), there is a second lower case "thunderbird" process that causes 50-150% CPU usage in the two processes. Also if I quit with both processes active I get an error message that "thunderbird" has unexpectedly quit. If I quit the "thunderbird" process with Activity Monitor the CPU issues go away for as long as the Thunderbird app is open. I found this exact issue as a reported bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1977514&_gl=1*1coyjyr*_ga*ODYxNzE0NjQyLjE2OTY0NDU3MDg.*_ga_2VC139B3XV*czE3NTY2OTAwOTckbzMkZzEkdDE3NTY2OTAyMzYkajI0JGwwJGgw It says that it was fixed, though, and it has not been for me. Does that mean it's only been fixed in versions not yet released, or is it already (incorrectly) believed to be fixed for everyone? Thank you.
Sarin'efijery napaingotra

All Replies (1)

Ed
Ed
  • Top 25 Contributor
more options

The bug is indeed fixed, but it may take a little while to land in the release versions.

Helpful?

Mametraha fanontaniana

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.