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.

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

  • 3 antwoorde
  • 6 hierdie probleem
  • 2 views
  • Laaste antwoord deur 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!

Gekose oplossing

vastator,

What were you able to determine?

Lees dié antwoord in konteks 👍 0

All Replies (3)

more options
more options

Gekose oplossing

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.