Closed Bug 1772565 Opened 3 years ago Closed 3 years ago

hangs upon launch on Mac OS 12.4 Intel - (going to +100% CPU load immediately)

Categories

(Thunderbird :: Untriaged, defect)

Product:
Thunderbird
Component:
Untriaged
Version:
Thunderbird 102
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: tattles-01.undo, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS 12; rv:86.0) Gecko/20100101 Firefox/94.0

Steps to reproduce:

Click the app icon

Actual results:

Opens in new look (after update), starts loading mail while going to +100% CPU load and freezing forever.

Expected results:

regular launch

What happens if you START

Flags: needinfo?(tattles-01.undo)

Yes, Mac Address Book IS enabled.

In troubleshoot mode, Thunderbird does not appear to freeze as soon, but CPU load continues to stay at around 100%, soon fans start getting louder… — not sure how long it will keep running.

Flags: needinfo?(tattles-01.undo)

OK, after 3rd try TB now stays stable in Troubleshoot Mode.

Tried disabling all add-ons for now and re-starting in regular mode.
Add-ons still disabled.
But did not help with the outcome.

Blocks: tb102found

Did you try the "reset toolbar" option that shows in the troubleshoot mode dialog? Please backup data first, in case it works so we can figure out what the problem was.

Yes I did. Still freezes equally as fast in Troubleshoot Mode as without.

Is there any kind of log file I can provide to help tracking down the root cause ?

And still nothing better with beta4 of it.

Now ramps up resource acquisition even faster with beta 5.

All persists through beta 7.

Only seems to occur while online. App is stable while offline.

Complete app freeze especially when some RSS endpoints cannot be reached.

CPU load now continuously at 97%.

Beta7: Resource usage still >100% but does not freeze anymore.

Beta 8: Back to full immediate freeze.

Problem persists in the release version. TB still completely unusable.

Uses up resource even faster upon launch with 103b1.

No improvement at all in 103b3 as well.

103b4 anyone ?

103beta5: Still the same. All fine, as long as offline. As soon as I switch to online mode, resource usage ramps up until complete freeze.

(In reply to Bardo Nelgen from comment #2)

Yes, Mac Address Book IS enabled.

In troubleshoot mode, Thunderbird does not appear to freeze as soon, but CPU load continues to stay at around 100%, soon fans start getting louder… — not sure how long it will keep running.

b6 is out.
let's see what is happening
start in troubleshoot mode.
immediately file > offline > offline mode
settings > general > scroll to disk space > uncheck compact all folders
open tools > error console
tools > activity manager
immediately file > offline > online mode

Activity Manager states: "Indexing 5 of 5288 messages in Inbox (0% complete)" — counting…

The error log goes like:

22:29:21.908 services.settings: Failed to load last_modified.json: TypeError: NetworkError when attempting to fetch resource. Utils.jsm:333
22:29:23.952 1658348963952 addons.xpi WARN Checking /Applications/Thunderbird.app/Contents/Resources/distribution/extensions for addons
22:29:25.602 Successfully loaded OpenPGP library librnp.dylib version 0.16+git20220124.f06439f7.MZLA from /Applications/Thunderbird.app/Contents/MacOS/librnp.dylib RNPLib.jsm:103:15
22:29:25.684 Found 0 public keys and 0 secret keys (0 protected, 0 unprotected) RNPLib.jsm:304:15
22:29:25.685 Trying to load /Applications/Thunderbird.app/Contents/MacOS/libotr.dylib OTRLib.jsm:64:11
22:29:25.770 Successfully loaded OTR library /Applications/Thunderbird.app/Contents/MacOS/libotr.dylib OTRLib.jsm:72:13
22:30:15.917 feeds: downloaded: updates disabled due to error, check the url - http://www.timeout.com/london/blog/feed.rss FeedUtils.jsm:1948:27
22:30:15.975 feeds: downloaded: updates disabled due to error, check the url - https://filmmusic.io/rss FeedUtils.jsm:1948:27
22:30:16.031 feeds: downloaded: updates disabled due to error, check the url - http://bizzenergytoday.com/feed FeedUtils.jsm:1948:27
22:30:16.032 feeds: downloaded: updates disabled due to error, check the url - http://green.wiwo.de/feed/ FeedUtils.jsm:1948:27
22:30:16.061 feeds: downloaded: updates disabled due to error, check the url - http://blogs.adobe.com/digitalmarketing/feed/ FeedUtils.jsm:1948:27
22:30:16.063 feeds: downloaded: updates disabled due to error, check the url - http://blogs.adobe.com/creativecloud/feed/ FeedUtils.jsm:1948:27

Some more feeds following.

CPU load currently at 102%, though not frozen over so far; despite still online.

Hope, this helps.

Now, that it does not freeze anymore, I can actually look at the activity manager, what it's doing:

Seems, the indexing is eating all this power, working at a speed of only around 100 messages / hour !!

Shouldn’t indexing be something capable of running in the background, rather than using ALL aof the computers available performance ?

Indexing throttles itself to provide some user responsiveness. Seeing indexing activity manager is fine even at high CPU as long as you are getting reasonable response time.

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

NO. It does not.

The Thunderbird folder in my OS Library is a funny 6.320.425.825.061 bytes large since it’s done indexing.

That’s more than 6.5 terabytes !!

Still don’t think we have a problem here ?

It’s the nstmp-file of an IMAP profile, which – at the time of being created – obviously used an IP address to connect to the server, rather than a domain / server name (obviously has been changed somewhen meanwhile…). Not sure the latter has anything to do with the cause; but it stands out.

(In reply to Wayne Mery (:wsmwk) from comment #23)

Indexing throttles itself to provide some user responsiveness. Seeing indexing activity manager is fine even at high CPU as long as you are getting reasonable response time.

Please have a look into this again. (see my comment above)

BTW hit the wrong key when typing 6.5… ;-)

Deleted the file, as the OS kept throwing out-of-diskspace warnings at me.

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