Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

Kërkoni te Asistenca

Shmangni karremëzime gjoja asistence. S’do t’ju kërkojmë kurrë të bëni një thirrje apo të dërgoni tekst te një numër telefoni, apo të na jepni të dhëna personale. Ju lutemi, raportoni veprimtari të dyshimtë duke përdorur mundësinë “Raportoni Abuzim”.

Mësoni Më Tepër

Progressively slowing down, massive memory leaks, message pane blacking out

  • 3 përgjigje
  • 6 e kanë hasur këtë problem
  • 2 parje
  • Përgjigjja më e re nga vastator

more options

Hi Everyone, just recently happened after the last update to 52.1.1 - has been fine for years prior.

The more messages I scroll through / read, the slower Thunderbird becomes, to the point where the message pane simply remains black and does not show the next message. At that point I need to either quit or force close Thunderbird,

Memory usage goes up - 183 MB at load time, around 700 MB after viewing 20-25 messages then crashes a little beyond that. Suspect it's the memory leaks driving the black message panes and slowness.

Happens during safe mode as well - so not the add-ons.

Any insights would be appreciated!

Hi Everyone, just recently happened after the last update to 52.1.1 - has been fine for years prior. The more messages I scroll through / read, the slower Thunderbird becomes, to the point where the message pane simply remains black and does not show the next message. At that point I need to either quit or force close Thunderbird, Memory usage goes up - 183 MB at load time, around 700 MB after viewing 20-25 messages then crashes a little beyond that. Suspect it's the memory leaks driving the black message panes and slowness. Happens during safe mode as well - so not the add-ons. Any insights would be appreciated!

Zgjidhje e zgjedhur

vastator,

What were you able to determine?

Lexojeni këtë përgjigje brenda kontekstit 👍 0

Krejt Përgjigjet (3)

more options
more options

Zgjidhja e Zgjedhur

vastator,

What were you able to determine?

more options

I couldn't solve it as above, but what I did was downgrade to 52.1.0 and re-upgrade.. seemed to fix it.