Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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

This thread was archived. Please ask a new question if you need help.

After sitting idle for awhile, a running Thunderbird App freezes on MacOS Mojave.

  • 2 replies
  • 1 has this problem
  • 3 views
  • Last reply by manenberg

manenberg
manenberg
more options

I believe this started only after upgrading to Mojave. Thunderbird runs fine for awhile, then come back to the App after an hour or two of idle and the App is nearly frozen. It will eventually respond to a few clicks and then the UI responds eventually but out of sequence to clicks. The only work around is to quit the App and relaunch it. I've reinstalled it a few times.

I believe this started only after upgrading to Mojave. Thunderbird runs fine for awhile, then come back to the App after an hour or two of idle and the App is nearly frozen. It will eventually respond to a few clicks and then the UI responds eventually but out of sequence to clicks. The only work around is to quit the App and relaunch it. I've reinstalled it a few times.

All Replies (2)

Wayne Mery
Wayne Mery
  • Moderator
  • Top 10 Contributor
more options

What version of Thunderbird are you running? And what add-ons?

manenberg
manenberg Question owner
more options

No extensions. It seemed to be broken for most of 60.* including 60.4 running on Mojave. It got fixed in 65.0 Beta. However, it "may" have broken again on 65.0Beta2. Will verify.