1823435 - Massive ram leak after update to 111

Status: RESOLVED WORKSFORME

(Core :: Performance, defect)

Description

[mattn]

Attachment: memory-report-troubleshoot.json.gz

Steps to reproduce:

From what I can tell, it happens everywhere. When I start using the browser, even with 1 or 2 tabs, if I just move around like going to google something and opening a link.

I have already tried to use troubleshoot mode, and resetting firefox to the factory, neither fix it. I have a memory report of the browser in normal mode, but I only attached the memory report from troubleshoot mode.

Actual results:

The page will not fully load and absolutely suck up all of my ram. It even goes into the swap until I close it with task manager, I have not let it run long enough to soak up all of the swap memory though.

Expected results:

It should not suck up all of my ram. It should also actually finish loading the page.

Comment 1

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

The Bugbug bot thinks this bug should belong to the 'Core::Performance' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Olli Pettay [:smaug][[e-mail]]]

Could you create a performance profile using https://profiler.firefox.com/ and share the profile then by clicking "Upload local profile" button in the profiler's user interface?

Also, is this a new issue, did this happen with Firefox 110?

Comment 3

[mattn]

I tried to reproduce it again. It is no longer happening, I just looked at my version, whatever was done in the new update for 111.0.1 has fixed it, but to answer your question, it did not happen in 110.

Comment 4

[mattn]

Nevermind, I have managed to trigger it again, it is now only happening on specific sites. Here is a link to a profiler while it was happening: https://share.firefox.dev/3n2Fbbm

Comment 5

[Olli Pettay [:smaug][[e-mail]]]

Unfortunately there is basically nothing happening in that profile.
Do you happen to know any particular site where it is happening? And if you don't want to share that information publicly, maybe via email to me?
[e-mail]

Comment 6

[Donal Meehan [:dmeehan]]

Bug 1824332 also has a memory report attached

Comment 7

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

This bug was moved into the Performance component.

:mattn, could you make sure the following information is on this bug?

• ✅ For slowness or high CPU usage, capture a profile with http://profiler.firefox.com/, upload it and share the link here.
• ✅ For memory usage issues, capture a memory dump from about:memory and attach it to this bug.
• Troubleshooting information: Go to about:support, click "Copy raw data to clipboard", paste it into a file, save it, and attach the file here.

If the requested information is already in the bug, please confirm it is recent.

Thank you.

Comment 8

[Jared Hirsch [:jhirsch] (he/him) (Needinfo please)]

:fdoty, looks like we have this and the linked bug that point to a possible performance issue in 111. Could you take a look?

Comment 9

[Frank Doty [:fdoty]]

Updating the Performance Impact flag to include this bug in perf triage for review

Comment 10

[Donal Meehan [:dmeehan]]

Settings 111 to wontfix, as 112 RC builds next week.
We should set 112/113 status flags pending the investigation results (see comment 9)

Comment 11

[Andrew McCreight [:mccr8]]

Unfortunately I don't see anything particularly high about the memory usage in the report. Maybe the high memory usage is happening in a process that is failing to respond. There's about 290MB of swgl memory, but that doesn't sound anywhere near as bad enough to explain the issues described in comment 0.

Comment 12

[mattn]

I'm unsure of what has been updated from 111 to 114, but 112, and 113 were a problem still and 114 has entirely resolved the issue.

Comment 13

[Andrew McCreight [:mccr8]]

Thanks for the update. I'm glad the problem went away for you.