Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

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.

تلاش سپورٹ

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.

مزید سیکھیں

Memory Leak /Ghost Tabs still happening in FF28

  • 4 جواب دیں
  • 56 میں یہ مسئلہ ہے
  • 10 دیکھیں
  • آخری جواب بذریعہ Rigin Oommen

more options

I have restarted, updated to 28 beta, turned off all add-ons, turned off hardware acceleration, made tabs load only when open, but STILL Firefox is sucking up to 6GIGs of memory.

This leak just grows and grows and grows. about:memory shows resources being used by tabs that I have already closed. java etc. from those pages are still running despite them being closed over an hour ago.

I know this has been a problem for years but good lord is it not time to fix it?!

I have restarted, updated to 28 beta, turned off all add-ons, turned off hardware acceleration, made tabs load only when open, but STILL Firefox is sucking up to 6GIGs of memory. This leak just grows and grows and grows. about:memory shows resources being used by tabs that I have already closed. java etc. from those pages are still running despite them being closed over an hour ago. I know this has been a problem for years but good lord is it not time to fix it?!

تمام جوابات (4)

more options
more options
more options

I did create a new profile, but that was on FF27, before I saw the thread that said to go to FF28 beta.

So now I've created a new one on FF28 and so far - fingers crossed - it is holding below 600mb. This is a megaton of memory for just 5 or 6 tabs, but it doesn't seem to be creeping steadily upwards to 6gigs... which is where it of course grinds to a halt.

Thanks, doing that again might have fixed it.

more options

type about:memory in address bar and perform analysis of the memory allocation.