1833296 - High WebExtensions memory usage with YouTube

Status: NEW

(WebExtensions :: Untriaged, defect)

Description

[vmoutsop]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/113.0

Steps to reproduce:

Normal usage, no more than 3 tabs open, 1 search, 1 youtube, 1 protopage.

Actual results:

Memory usage goes over 4gb within minutes

Expected results:

Memory usage on a per process level not higher than 2-300MB

Comment 1

[vmoutsop]

User agent: 2b694d1da5354999aab240ed4e4a1195

Comment 2

[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 3

[vmoutsop]

The issue seems to be primarily once YouTube is opened in a tab. Not only does memory usage jump to 2-4GB of memory usage, at that point the time to open a non YouTube page in a tab goes from a normal 0-5 seconds to 30-60-90 seconds or more.

This bugzilla page took over 60 seconds to load so I could enter this comment after restarting Firefox. I've gone in and minimized memory usage, I've deleted content-prefs.sqlite file and it doesn't seem to have an effect. This started getting worse over the past few updates and now it is almost unbearable.

I have installed versions and portable firefox versions, both are equally having the same issue.

Comment 4

[Andrew McCreight [:mccr8]]

What OS are you using? Please attach a memory report from about:memory. It will include URLs of open pages unless you check "anonymize".

Are you using any Firefox themes with animation, like Dark Space? That has been causing issues for people.

Comment 5

[vmoutsop]

Windows 10 Pro 64. Using default "Dark" theme.

Uh, how do I attach a memory dump, I don't see an attach file option?

Comment 6

[Andrew McCreight [:mccr8]]

Go to about:memory, possibly check "Anonymize", then click on "Measure and save". Then once you have a file, click on "Attach new file" on this bug. It is right above comment 0.

Comment 7

[Andrew McCreight [:mccr8]]

Ideally you'll want to get the memory report after the memory has started going up, but before your system becomes overloaded. It can be hard to get a memory report if things aren't responsive.

Comment 8

[vmoutsop]

Attachment: memory-report.json.gz

Comment 9

[vmoutsop]

Duh, sorry about that.

Comment 10

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

This bug was moved into the Performance component.

:vmoutsop, 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 11

[Andrew McCreight [:mccr8]]

The largest content process is using 300MB, which is a little high, but it isn't too unreasonable. The main process is in the same range.

It looks like your WebExtensions process is using about 1.2GB of memory. xpconnect/runtime is 110MB. I'm not sure I've ever seen a value that high before for that. Otherwise, no individual thing is that huge. Lots of JS Function, Call and Array objects.

I'm not really sure what the next step is for figuring out what might be causing the high WebExtensions memory. Maybe somebody who is more familiar with that has some ideas.

One thing to try would be to disable addons that deal exclusively with YouTube ("Enhancer for YouTube" and "Return YouTube Dislike") and see if one of them is causing the issue. "TWP - Translate Web Pages" is another one to try, as I do see a Chrome worker in the largest content process (translation/cld-worker.js) that could be related.

Comment 12

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

Redirect a needinfo that is pending on an inactive user to the triage owner.
:rpl, since the bug doesn't have a severity set, could you please set the severity or close the bug?

For more information, please visit BugBot documentation.