Vanwege onderhoudswerkzaamheden die uw ervaring zouden moeten verbeteren, heeft deze website beperkte functionaliteit. Als een artikel uw probleem niet verhelpt en u een vraag wilt stellen, kan onze ondersteuningsgemeenschap u helpen in @FirefoxSupport op Twitter en /r/firefox op Reddit.

Avatar for Username

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

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

  • 4 antwoorden
  • 3 hebben dit probleem
  • 1 weergave
  • Laatste antwoord van Mattanorak

Mattanorak
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!

Bewerkt door Wayne Mery op

Gekozen 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.

Dit antwoord in context lezen 👍 0

Alle antwoorden (4)

Wayne Mery
Wayne Mery
  • Moderator
  • Top 10 Contributor
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?

Mattanorak
Mattanorak Vraageigenaar
more options

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

Mattanorak
Mattanorak Vraageigenaar
more options

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

Mattanorak
Mattanorak Vraageigenaar
more options

Gekozen 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.