1830641 - Thunderbird with hanging connection to server (progress bar indicating activity) adds some 60% CPU core load

Status: RESOLVED INCOMPLETE

(Thunderbird :: General, defect)

Description

+++ This bug was initially created as a clone of Bug #562977 +++

You should not have closed that bug, and was not allowed to reopen it :-(

What I wrote 9 years ago (!) in bug 562977 comment 39 still holds (at least with version 102).

When trying to connect to a mail server where the connection hangs for some reason, CPU load increased by about 60% (of one core of my current Linux machine, but I had the bug also with MacOS).

The statement by :Paenglab at bug 562977 comment 83 that this cannot be reproduced is wrong.
Anyone interested can reproduce the issue in a straightforward way:
put any garbage IP address (e.g., 1.2.3.4) as the SMTP, IMAP, or POP server name and try sending (or receiving, respectively) emails.

There are numerous related issues/bugs, also with Firefox, since 10+ years.
It's a shame that this is still not fixed.

Comment 1

[Niklas Hambüchen]

Attachment: screenshot-of-throbber-cpu-usage.png

Attaching screenshot of 12% CPU usage.

Note that I believe that in the original bug that this one was cloned from, it was about a progress bar at the bottom.

In my current Thunderbird 102.9.0 on Linux, I get a jumping throbber symbol in the top left instead, and don't know whether I can make the progress bar appear any more.

Another curious thing:
When I try to record a video of it using "simplescreenrecorder", the CPU usage drops to 5% exactly while the capture is running.

Comment 2

[David von Oheimb]

BTW, Betterbird connections exhibit the same crappy busy waiting behavior wasting a CPU core and laptop battery
while Evolution works fine, to which I switched since these and many other notorious Mozilla bugs are not fixed for 10+ years.

Comment 3

[Wayne Mery (:wsmwk)]

wanted https://support.mozilla.org/en-US/kb/profiling-thunderbird-performance

Comment 4

[David von Oheimb]

Related bug reports include bug 683651 and bug 1107251

Comment 5

[Wayne Mery (:wsmwk)]

Thank you for finding those bug reports.

If the issue is one of those bugs, then there is nothing to be done in this bug. We should either close this or dupe to one of those bug reports - we don't need two bugs covering the same issue.
If, after they are fixed, you still see an problem, then we can reopen this bug. So for now we can call this incomplete.