1931914 - Firefox 133 and 134 betas repeatedly use excessive memory and hang when releasing

Status: NEW

(Core :: Performance: Memory, defect)

Description

[Peter Janes]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:133.0) Gecko/20100101 Firefox/133.0

Steps to reproduce:

Using the browser as usual (create new tabs/windows, load pages, navigate, use forms, type in search, etc.). No detectable pattern in when excessive allocation occurs.

This has been an issue since I updated to the 133 beta, i.e. it wasn't present in 132 beta or release.

Actual results:

Browser hangs (beachball) for several seconds every 5-10 minutes, then continues as usual. In a "top" window I see the memory usage increasing dramatically (1G every second or two) and then it hangs while the memory usage drops.

https://share.firefox.dev/3OfKT4g

Expected results:

No recurring excessive memory usage.

Comment 1

[Andrew McCreight [:mccr8]]

It looks like the CPU time is being spent freeing StructureCloneBlob::Holder. I'm not sure what that means.

Comment 2

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

This bug was moved into the Performance component.

:bugzilla-mozilla-20220926, 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 3

[Peter Janes]

Attachment: memory dump (memory-report.json.gz)

Memory dump as requested.

Comment 4

[Peter Janes]

Attachment: troubleshooting information

about:support troubleshooting information, as requested.

Comment 5

[Peter Janes]

The problem persists in Firefox 134 beta; do you need similar information, or is the 133 information sufficient?

Comment 6

[Frank Merla]

I am experiencing a similar issue with firefox 134.0.1 (Windows). Memory usage (just with a single tab open), cash cleared rises steadily until the system runs out of memory (only forcefully closing firefox) allows the system to function normally again.

Comment 7

[Peter Janes]

Firefox 135 and 136 beta, and 135 release, are also affected. Is additional information required?

Comment 8

[Markus Stange [:mstange]]

Peter, your about:memory report attributes a lot of the parent process memory to an extension with the ID {c5f935cf-9b17-4b85-bed8-9277861b4116}, which appears to be an add-on called "Allow CORS: Access-Control-Allow-Origin". Can you check if disabling this add-on improves the situation?

Frank, the issue you're experiencing is likely to have a different cause, could you file a new bug about it please?

Comment 9

[Peter Janes]

Thanks, I'll give that a try. I've also submitted a bug report to the addon developer referencing this issue.

Comment 10

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

The severity field is not set for this bug.
:jlink, could you have a look please?

For more information, please visit BugBot documentation.