1655176 - Memory leak in webpage styling

Status: RESOLVED INCOMPLETE

(Core :: Graphics, defect)

Description

[Xesxen]

Attachment: memory-report.json.gz

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

Steps to reproduce:

Open up https://www.anime-planet.com and keep the tab open.

Actual results:

The memory usage of Firefox, both on Windows and Linux, will rise keep rising until it freezes the system (due to swapping) On both operating systems, this memory increase is happening with about 100MB/s .

Other subpages of the site don't have the same behaviour, and the memory snapshot does not show this leaked memory (it reports ~15MB of memory usage). Chromium doesn't show the same behaviour and will keep the site at a constant memory usage.

Changing the tab to something else temporarily stops the memory increase until the tab is active again.

The memory report attached is from an (Arch) Linux system running Firefox 78.0.2.

Expected results:

The memory usage should've become constant after the page has fully loaded.

Comment 1

[feinraf]

Can reproduce this in Windows 10 Pro running Firefox 78.0.2. My memory-report is attached.

Comment 2

[feinraf]

Attachment: memory-report.json.gz

Comment 3

[Pablo]

Hi Xesxen

I tried this today with the latest release version 79 on windows10 64bit and i am unable to reproduce.
I Left the website open for some minutes and the memory did not increase too much. (see screenshot attached)

Can you tell me what addons do you have installed?
Can you try again updating firefox to the latest release version79 ?
Or you can also download the latest Firefox Nightly from here: https://nightly.mozilla.org/ and retest the problem.

If you still have the issue please create a new profile, you have the steps here:https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles?redirectlocale=en-US&redirectslug=Managing-profiles#w_starting-the-profile-manager

Lastly test if the issue is reproducible in safe mode, here is a link that can help you:
https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode

Regards

Comment 4

[Pablo]

Attachment: memory.jpg

Comment 5

[Xesxen]

Attachment: memory-report-linux-nightly-81.0a1.json.gz

Comment 6

[Xesxen]

Attachment: Screenshot from 2020-07-28 22-18-32.png

Comment 7

[Xesxen]

Hi Pablo,

I've attached a new memory report and a screenshot from the browser+task manager using Firefox Nightly 81.0a1 on Linux. This is using a clean profile with no extensions added. The memory increase is still present unfortunately.

Best regards,

Comment 8

[feinraf]

Attachment: Windows 10 firefox nightly ram usage

Hi Pablo,

I've also attached a new screenshot with my task manager in Windows 10 with the latest Firefox Nightly, fresh profile, no extensions. 81.0a1 (2020-07-28) (64-bit)

The memory increase is still present.

Thank you.

Comment 9

[Xesxen]

I've noticed the same behaviour also occurs when you pop out the Youtube livestream chat (https://www.youtube.com/live_chat?is_popout=1&v=VIDEOID) and put it to fullscreen (1080p in my case). The memory usage increase for youtube is about 50MB/s.

However, as soon as I make the window smaller (covering ~50% of my 1080p screen) the memory increase will stop and instead will start to reclaim the memory it previously allocated when the window was fullscreen. Resizing the window to ~95% screen coverage still leads to the memory increase happening.

To me this sounds like the renderer creates new objects for every frame as stuff gets changed, but the GC is not able to keep up with the rate of these objects being created. To add some detail: both at fullscreen and 50% screen coverage one of the threads is near-100% CPU (single core) usage.

Comment 10

[Pablo]

this is interesting. I did again all the tests for https://www.anime-planet.com/
And i was able to replicate it but only 1 time using windows 10 and Firefox 80.0.1

On Windows10 64bit:
Firefox Release 80.0.1 : I did get a memory increase having just that window Open.
Firefox Beta 81.0 : Memory consumption was normal
Firefox Nightly 82.0a1 : Memory consumption was normal.

On Ubuntu 18.04:
Firefox Release 80.0.1 : Memory consumption was normal
Firefox Beta 81.0 : Memory consumption was normal
Firefox Nightly 82.0a1 : Memory consumption was normal.

Im wondering if you still have the problem using the latest nightly version or latest beta version.
Can you please let me know downloading it from https://nightly.mozilla.org/

thanks

Comment 11

[Pablo]

Hi Andrew how are you?

I was able to reproduce this memory bug only using Firefox release 80.0.1
Do you know what is the correct component i should set for this bug?

the memory report is attached.

thanks.
Pablo

Comment 12

[Andrew McCreight [:mccr8]]

This is in the first memory report: 10,301.02 MB (97.23%) ── heap-unclassified in the main process. This report does not have a GPU process, but there is some mention of webrender in the memory report. There's not really any more information beyond that.

In the second memory report, the main process looks normal, but this is showing up in the GPU process: 1,790.67 MB (97.81%) ── heap-unclassified.

The third report is similar to the first, with an entry like 3,716.63 MB (94.06%) ── heap-unclassified.

Based on the second report, I'm going to guess that this is related to graphics, possibly WebRender.

Comment 13

[Jamie Nicol [:jnicol]]

Hi Xesxen, Feinraf. Could you confirm whether setting gfx.webrender.force-disabled to true, and restarting, fixes the problem.

Comment 14

[Jamie Nicol [:jnicol]]

Also, do you know whether this affected older versions of Firefox too? Could you try running mozregression too see if you can find out which version of firefox introduced the problem? Thanks

Comment 15

[BugBot [:suhaib / :marco/ :calixte]]

Clear needinfos that are pending on inactive users.

Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.

For more information, please visit BugBot documentation.