1734644 - High JS memory usage on videnskab.dk

Status: UNCONFIRMED

(Core :: JavaScript Engine, defect, P3)

Description

[Gunnar Andre]

Attachment: firefox-memory leakage.jpg

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4606.71 Safari/537.36 Edg/94.0.992.38

Steps to reproduce:

Easy to replicate, If I have 30 tabs open and open https://videnskab.dk/ (science page) and let it stay open for some hours it have consumed a lot of memory.
Look at the atteched fil, "minne" in norwegian is memory. It have been like this for a long time. I use version 93. Windows version 10, 20H2.
I think it happen because of never ending loading of ads

Actual results:

Firefox respond slower and slower, I have to kill the offending firefox proccess, and the page crashes of course. And I can continually use firefox

Expected results:

It should work normaly. I can help testing if you like.

Comment 1

[Simona Badau, Desktop QA]

Andre, could you please try to create a memory report? Here is what you need to do:

1. Wait until Firefox is consuming a large amount of memory.
2. Enter about:memory in the URL bar and press enter.
3. Click "Measure and save" (optionally with "anonymize" checked to hide URLs, although this will likely make it more difficult for us to figure out which site, if any, is causing the leak).
4. Save the memory report somewhere.
5. Attach the report to this bug.

Thanks!

Comment 2

[Gunnar Andre]

Attachment: memory-report.json.gz

Hi, the offending firefox.exe process took about 900MB and still growing and the url is https://videnskab.dk/ (popular science page). Easy to replicate, just let it say up for a while with other tabs. Usually the firefox processes takes 250 to 350 MB .

Comment 3

[Simona Badau, Desktop QA]

Andrew, when time permits, could you please take a look at the memory report attached above? Also, based on it, could you help with the setting of the right component? Thanks!

Comment 4

[Andrew McCreight [:mccr8]]

There's a detached window with around 500MB of mostly JS stuff. Maybe this is a duplicate of the weak map leak issue? It has a similar feel to it.

Comment 5

[Jon Coppeard (:jonco)]

(In reply to Gunnar Andre from comment #0)
I couldn't see any leak after a few minutes, but I'll leave it open over night to check.

We did recently fix a memory leak in bug 1717553. Could you test this with the latest nightly to see the problem happens there?

Comment 6

[Jon Coppeard (:jonco)]

Well, it seems to still be happening. Original footprint:

303.31 MB (100.0%) -- explicit
├──134.04 MB (44.19%) -- window-objects
│  ├──131.22 MB (43.26%) ++ top(https://videnskab.dk/, id=27)
│  └────2.82 MB (00.93%) ++ top(none)/detached

16 hours later, after minimizing memory:

3,758.86 MB (100.0%) -- explicit
├──3,238.30 MB (86.15%) -- window-objects
│  ├──2,079.32 MB (55.32%) ++ top(none)/detached
│  └──1,158.97 MB (30.83%) ++ top(https://videnskab.dk/, id=27)

Comment 7

[Gunnar Andre]

Hi !
I installed the nightly version 95.0a1 (2021-10-14) (64-bit) and after a few hours with some tabs open including videnskab.dk and it consumed a lot of memory. So its still there but it looks like it goes slower