Thunderbird Mac freezes on startup (and a workaround).
I wanted to share a specific startup freeze loop I encountered today.
I had a moderate number of tabs open in Thunderbird when I quit the app. I had set up a single IMAP message filter yesterday to automatically move incoming automated text alerts into their own folder (causing about 50–60 small emails arriving in quick succession this morning at startup).
The Problem: Upon starting up, the app almost immediately choked and became unresponsive. Unlike the freeze report by another user here on August 21st.
My Workaround: After a few attempts to open Thunderbird I managed to break the freeze loop by instantly closing the single open UI window right at startup. This kept T-bird running invisibly in the macOS background. It seemed that without the need of rendering the UI, the background engine successfully completed all the IMAP syncing and filtering tasks.
When I brought Thunderbird back to the foreground, all my open tabs instantly "snapped", and the app has been perfectly stable since. I haven't tried to replicate this due to the fear of breaking the current stability.
Has anyone else recently noticed Thunderbird freezing under similar conditions lately? Let us know if this workaround helps you get past your startup freezes too!
All Replies (2)
Isisombululo Esikhethiwe
UPDATE: I checked my Message Filter settings and found some possible causes. I had checked "Manually Run", "Periodically", and "Getting New Mail" all at the same time. This seemed to trigger a data-handling conflict under a heavy load.
Looking at my macOS diagnostic logs, the failure unfolded in just 2.25 seconds: - 10:22:33.14: The network hub is acutely overloaded by a sudden flood of IMAP data. - 10:22:33.65: iCloud security hits a timeout because it cannot process the authentication tokens rapidly enough. - 10:22:35.39: Local KeySync triggers a hard lock, permanently freezing the application process.
Making these filter checkbox options mutually exclusive could maybe prevent users from accidentally creating conflicting background loops.
The real, structural solution though is, Mozilla could implement something like decoupling the startup of the visual interface, downloading e-mail, and the background filtering tasks at the same instant.
More testing would need to be done to find the root cause.
Edit: The problem solved itself after the next time quiting the app and after a 'Compact Folders' of the account involved.
[Note: Troubleshooting and formatting done with the assistance of a free AI tool based on my local macOS Console logs and reconstruction of the events.]
Okulungisiwe ngu Seb Mac
In my case, I had not created any specific IMAP filters. However, I had opened two attachments from one particular message, and these two attachments seem to have been causing the freeze loop on startup. The only way I was able to get out of it was by following Seb Mac's suggestion. These were the actual steps I took: (1) ran Force Quit to kill Thunderbird. (2) restarted Thunderbird, but at the moment the Thunderbird window appeared on the screen, before any detail had been rendered, I hit Command-Q. This effectively killed Thunderbird a second time. (3) restarted Thunderbird again. Upon this second restart, there was no freeze loop. All pre-existing tabs were still present, but empty. I right-clicked on my default Inbox tab, clicked Close Other Tabs, and thereafter Firefox behaved normally.
Okulungisiwe ngu jefnik3
You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.