Questo sito potrebbe offrire funzionalità limitate durante le operazioni di manutenzione per migliorare l'esperienza utente. Se un articolo non risolve il tuo problema e vuoi richiedere supporto, la nostra comunità di supporto è pronta ad aiutarti tramite @FirefoxSupport su Twitter e /r/firefox su Reddit.

Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

Why is composing messages suddenly painfully slow?

more options

Composing email messages in Thunderbird has suddenly become painfully slow. Rebooting my computer (iMac running OS X Yosemite) and uninstalling and reinstalling Thunderbird has not helped. When I type words into the message window, I can't see what I did until I hit command ` twice to go to the main window and back to the message window. This makes it take a very long time to compose even a simple message to send.

Composing email messages in Thunderbird has suddenly become painfully slow. Rebooting my computer (iMac running OS X Yosemite) and uninstalling and reinstalling Thunderbird has not helped. When I type words into the message window, I can't see what I did until I hit command ` twice to go to the main window and back to the message window. This makes it take a very long time to compose even a simple message to send.

Tutte le risposte (1)

more options

Not a Yosemite Expert but that appears to be a focus-stealing issue on Mac OSX itself. The clicking _ ` _ is manually refocusing the 'main window' which I'm understanding from your post to be the ``Compose Window`` but as to why it is lagging does not seem to be Thunderbird's cause, consider looking at disk i/o during a replication session, and/or with a clean profile:

Clean profile being you copy/backup your present config `folder` and move outside its present directory and reload. If it persists it's not a user config issue if not it is something in your present config that has corrupted or misconfigured itself.