1683978 - Leaks a ton of memory on Facebook.com after using for a while

Status: UNCONFIRMED

(Core :: JavaScript Engine, defect, P2)

Description

[Steve]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:84.0) Gecko/20100101 Firefox/84.0

Steps to reproduce:

Opened browser, load facebook.com Scroll through facebook, comment, refreshing etc.

Actual results:

After a while open the memory surges into the gigabytes and gigabytes used and the browser will then start to become unresponsive and slow. I will eventually have to close the browser to resolve the problem, then re-open. Then it works fine until it happens again. I have tried to duplicate this in Chrome and it doesn't happen so it's clearly something in Firefox and not system related. Tried a removal and reinstall of Firefox but still causes the problem.

Expected results:

I'm not expecting increased memory usage over time but the amount it surges to after spending a while on Facebook.com is a problem. It certainly shouldn't grow to 6-10gb of memory usage when typically it uses 500mb.

Comment 1

[Steve]

Attachment: This is the memory that has leaked after 1 hour of use on Facebook.com

1 Hour of memory consumption (leak) on Facebook.com. If I close the browser and re-open to facebook.com it comes back at 440mb (approximately)

Comment 2

[Steve]

Attachment: Facebook Idle for 8 hours.

Facebook.com idling for 8 hours with no navigation or usage of the site.

Comment 3

[Andre Klapper]

Please enter the address
about:memory?verbose
in the address bar and attach (using the "Attach New File" link above) the output here.

Comment 4

[Steve]

Attachment: Memory Log

Comment 5

[Steve]

I uploaded I think what you are looking for. Let me know if it's not correct.

Comment 6

[Negritas Sergiu, Desktop QA]

Hello unfortunately i wasn't able to reproduce the issue with firefox 86.0a1(2020-12-22) with Ubuntu 20.
Andrew can you please take a look at this issue?

Comment 7

[Steve]

Since the update to 84.0.1 it seems better (might be anecdotal) but it's still happening.

Comment 8

[Andrew McCreight [:mccr8]]

Thanks for the memory report. There's almost 700MB of JS classes, so this is probably a duplicate of bug 1675837 or one of the many other bug reports we've gotten about high JS class memory usage on Facebook.

Comment 9

[Steve]

Is there a way to have Firefox better manage aging Java Script to keep this under control? Because closing the Facebook tab and waiting about a minute clears this from memory and then you can reload and resume Facebook until it fills up again.

Comment 10

[Andrew McCreight [:mccr8]]

To the best of my knowledge, this is an issue with Facebook itself that they are trying to resolve. Unfortunately it is hard to establish hard resource limits for pages, because the resources needed by a web page vary so much.

Hitting the reload button should also throw out the existing page and load a fresh copy, if you want a way to deal with it that is a little easier than closing and reopening the tab.

Comment 11

[Steve]

I appreciate that insight, I just thought if Firefox had a way to track how old content in memory was with regards to Java Script and could flush it so to speak after a period of an hour if it hasn't been accessed sort of thing.

Oh well... It is what is. Thanks for the reply. :)

Happy New Year.