Поиск в Поддержке

Избегайте мошенников, выдающих себя за службу поддержки. Мы никогда не попросим вас позвонить, отправить текстовое сообщение или поделиться личной информацией. Сообщайте о подозрительной активности, используя функцию «Пожаловаться».

Подробнее

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

  • 4 ответа
  • 3 имеют эту проблему
  • 1 просмотр
  • Последний ответ от 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!

Изменено Wayne Mery

Выбранное решение

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.

Прочитайте этот ответ в контексте 👍 0

Все ответы (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

Выбранное решение

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.