1925736 - 12GB+ memory leak in an extension. About:memory shows tons of similar data:image /png base64 URIs (Was: Memory leak in Ubuntu 24.04 // Firefox 131.0.2)

Status: UNCONFIRMED

(Core :: Performance, defect)

Description

[set.tobur]

Attachment: memory-report2.json.gz

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

Steps to reproduce:

There isn't a specific way to trigger it. I normally only have firefox open, and if there is something else open is Files, or Sublime text.

I can be browsing through webs, and when I open one, I start noticing everything is starting to lag. The RAM memory icon at the top bar gets full, when 2 seconds ago was less than 50% full.

Sometimes I try to click and see how much memory ram has taken Firefox this time, although is not possible most of the time, since the computer lags, and doesn't answer my commands. This time I was able to do it, and Firefox was consuming 13Gb of 16Gb that the laptop has.

Actual results:

Other times the problem arise when I'm scrolling through a webpage, or reading it. When it has never happened is when I'm seeing a movie/anime/youtube...

And normally it fixes itself after couple minutes, seems like Firefox calling the garbage collector, but since it doesn't have RAM it takes a bit to clear it. Couple times happened that it closed the session of Ubuntu and I had to log in again.

Expected results:

Not even having this glitches, or interruptions, since I never have them with Chrome, and therefore is something exclusively of Firefox.

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

[Mayank Bansal]

Explicit Allocations

12,683,380,264 B (100.0%) -- explicit
├──12,587,269,872 B (99.24%) -- js-non-window
│ ├──12,508,148,296 B (98.62%) -- zones
│ │ ├──12,500,046,488 B (98.55%) -- zone(0x7f36a9a3be00)
│ │ │ ├──12,449,890,224 B (98.16%) -- strings
│ │ │ │ ├─────211,358,448 B (01.67%) -- string(length=23417, copies=4298, "data:image/x-icon;base64,AAABAAQAMDAAAAEAIACoJQAARgAAACAgAAABACAAqBAAAO4lAAAYGAAAAQAgAIgJAACWNgAAEBAAAAEAIABoBAAAHkAAACgAAAAwAAAAYAAAAAEAIAAAAAAAgCUAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAP///0X///+Z////zP////P////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////w////zP///5P///8/AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAD///8k////wP//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////t////x4AAAAAAAAAAAAAAAAAAAAAAAAAAP///0L////z///////////////////////////////////////////////////////////////////////////X7///u+T//5DV//+R1f//csr//1C+//+Cz///kdX//5/Z///L6v//8vr//////////////////////////////////////////////////////////////////////////////////////+3///85AAAAAAAAAAAAAAAA////Lf////D///////////////////////////////////////////////////////////////+85f" (truncated))
│ │ │ │ │ ├──211,255,296 B (01.67%) ── malloc-heap/two-byte

This is all memory used in extension. What extensions do you have?

1. Type "about:support" in your browser and copy-paste its contents here
2. Disbale all your extensions and enable them individually one-by-one to see enabling which one causes the memory issue.

Comment 3

[set.tobur]

Attachment: about:support output

Comment 4

[set.tobur]

Once I tried to disable most of the extensions, and I think I even disabled ublock, which I feel could be the problem, but still the ram didn't come back to the original value right away. So, I suppose I should be all the time without ublock to test it, but without it browsing is... painful xD

Comment 5

[Mayank Bansal]

sorry, i wasnt clear enough.

What I meant was to all disable all addons. Then enable one addon and browse the way you normally do. Then see if the large memory use is reproducible. If you dont see the increased memory, disable the first addon, enable the second one and restart Firefox and browse. Keep on doing this till you can identify the addon that causes the memory use.

(Instead of enabling them one by one and testing ,it may be faster to disable half of them and then test. If it reproduces, disable half of the current addons and retest. If it doesnt repro in the first half, disable that set adn enable the second half and retest. And so on. Almost like a binary search)

Comment 6

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

This bug was moved into the Performance component.

:set.tobur, 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 7

[set.tobur]

Attachment: raw data of about:support

Comment 8

[set.tobur]

The data of about:support was uploaded before, but I just took another copy of it and uploaded it. Both were done when the ram was in it's normal state.

I'm trying to get the information about the plugins, and I suppose the profiler info. But for now I haven't had the bug or the memory leak yet, so I'm waiting until it happens. Lately I have been traveling a bit, so maybe I haven't been using the laptop that much.

Comment 9

[Mayank Bansal]

:robwu and :rpl, you may have some opinion here?