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.

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

Hierdie gesprek is in die argief. Vra asseblief 'n nuwe vraag as jy hulp nodig het.

Key combinations slow down thunderbird (Mac). CAUSE: ram

  • 4 antwoorde
  • 3 hierdie probleem
  • 1 view
  • Laaste antwoord deur Mattanorak

more options

Hi,

By this, I mean that in TB, if I close a message by clicking CMD-W (standard close Window keystroke), I get a beachball and then eventually the window closes. In fact, if I do anything with keyboard shortcuts (CMD-N for New Message, CBD-B for Bold text, etc), then TB waits for a while, the beachball spins, the CPU usage goes up and eventually it's released and carries on.

I found as a workaround, don't use the keyboard shortcuts (not ideal), so click File, Close to close the window, click on the B icon to make the text bold, etc.

The same happens in TB safe mode. 52.6.0 (64-bit)

Anyone else seen this - and know of a solution, please? Thanks!

Hi, By this, I mean that in TB, if I close a message by clicking CMD-W (standard close Window keystroke), I get a beachball and then eventually the window closes. In fact, if I do anything with keyboard shortcuts (CMD-N for New Message, CBD-B for Bold text, etc), then TB waits for a while, the beachball spins, the CPU usage goes up and eventually it's released and carries on. I found as a workaround, don't use the keyboard shortcuts (not ideal), so click File, Close to close the window, click on the B icon to make the text bold, etc. The same happens in TB safe mode. 52.6.0 (64-bit) Anyone else seen this - and know of a solution, please? Thanks!

Gewysig op deur Wayne Mery

Gekose oplossing

Well, wouldn't you know it... I decided to reset the PRAM to see if that made any difference and it didn't. So I did it again - and BINGO! Seems to have fixed the issue.

Lees dié antwoord in konteks 👍 0

All Replies (4)

more options

I've seen this reported before, and if I remember correctly is fixed by updating OS X. What version are you at now? Have you tried updating?

more options

I'm on the very latest (High Sierra 10.13.3), no updates waiting to be installed.

more options

There can't only be 2 of us that have this issue if it's an OS issue?

more options

Gekose oplossing

Well, wouldn't you know it... I decided to reset the PRAM to see if that made any difference and it didn't. So I did it again - and BINGO! Seems to have fixed the issue.