memory leak occurring on macOS 13.3.1 with animated theme
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
People
(Reporter: austinleeroddy, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(4 files)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.0.0 Safari/537.36
Steps to reproduce:
Steps:
- leave firefox open and running on my mac for a couple of days.
- after running for about ~2 days my system will run out of application memory due to firefox.
Actual results:
If I leave firefox open consistantly for about ~2 days or so I end up having to force close and reopen because a macOS error pops up saying that my system has ran out of application memory and that I need to close applications. When the 'close an application' box pops up firefox is always the culprit and macOS says it using around 90-120GB of application memory.
Expected results:
;_; firefox not use that much memory :). Firefox is 👑 aint no way im switching to something chrome based 😆
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Cocoa' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•2 years ago
|
||
Could you try to capture a Firefox profile with memory allocation tracking enabled, then upload the profile and share the URL here?
https://profiler.firefox.com/docs/#/./memory-allocations
Comment 3•2 years ago
|
||
I'm marking this as a See Also and not a dupe of bug 1828587, though it might be the same issue. It looks like the issue is being reported against 112, which is a point in its favor, but we don't have any information about where the memory usage is coming from, and "slow steady leak over a few days" isn't quite the same as "all memory gone in 2 hours when watching videos". Though maybe this user just has so much memory they don't notice the issue for longer.
Reporter | ||
Comment 4•2 years ago
|
||
Been away from my computer. I will capture browser info and update this soon!
Comment 5•2 years ago
|
||
Thanks. Do you have multiple monitors on your computer? I'm wondering because some other users (on Windows) have experienced memory issues with multiple monitors.
Comment 6•2 years ago
|
||
Another thing that seems to have caused memory issues for some users is the Dark Space theme, or any theme with animations.
Reporter | ||
Comment 7•2 years ago
|
||
Alright, attached to this, I included both the profiler log here (https://share.firefox.dev/41SkqhY), and I also attached the 'about:memory' report and my 'about:support' info. Last week firefox ran out of memory again and crashed, so I was able to also grab the log that macOS gave me in the 'firefox - crash report.txt' file.
I use a dual monitor setup for the other questions and have been using an animated "Dark Space theme." However, I will change off of that theme starting today. Usually, I've noticed the memory leak when I have many tabs open and multiple windows of Firefox open, some minimized. Since I haven't been using my browser as extensively recently, I haven't experienced a crash yet, but a couple of days ago I did run out of memory and ran the profiler for a little bit of time. I don't know if I should've run it for longer, but everything was lagging pretty hard before I force closed Firefox.
Yesterday when using Firefox I watched the memory usage, and it stayed where it should, 1-4GB, but I wasn't using it that extensively. Just one window open and a handful of tabs. I'll continue using my computer, and if I run out of memory, I'll run the profiler and add that info here too.
Reporter | ||
Comment 8•2 years ago
|
||
Reporter | ||
Comment 9•2 years ago
|
||
Reporter | ||
Comment 10•2 years ago
|
||
Comment 11•2 years ago
|
||
Emilio, is the backout going to help MacOS, or does that require fixes from the followup work?
Comment 12•2 years ago
|
||
It should help with the occluded window case, not the minimized window case
Updated•2 years ago
|
Comment 13•2 years ago
|
||
The component has been changed since the backlog priority was decided, so we're resetting it.
For more information, please visit BugBot documentation.
Updated•1 year ago
|
Comment 15•1 year ago
|
||
Redirect a needinfo that is pending on an inactive user to the triage owner.
:gw, since the bug has recent activity, could you please find another way to get the information or close the bug as INCOMPLETE
if it is not actionable?
For more information, please visit BugBot documentation.
Updated•1 year ago
|
Description
•