Memory leak since version 112
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
People
(Reporter: nasko235679, Unassigned)
Details
Attachments
(1 file)
36.97 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/113.0
Steps to reproduce:
Have multiple windows and tabs open.
Actual results:
Firefox starts using 100% of RAM (32 gigabytes) and even fills up windows page file. This leads to my entire system hanging and apps crashing. Usually the culprit is a single tab and I've actually managed to fix the leak by luck if I manage to close the exact tab that's causing the issue. I will attach a screenshot of a log I created in about:memory. From what I'm seeing something goes wrong with the --webrender and an insanely large image gets created in the -render-texture-hosts section. The memory values are way out of wack in that section of the log.
This log is from version 113 because after the bug first appeared in 112 I tried switching to the beta branch out of pure desperation.
Apologies that I'm not attaching the log itself, I forgot to anonamyze it before saving and now I have to wait for the bug to reappear again. When it does I will send the full log.
Expected results:
Firefox shouldn't leak memory.
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Graphics: WebRender' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•2 years ago
|
||
insanely large image gets created in the -render-texture-hosts section.
Going to dupe based on that.
Comment 3•2 years ago
|
||
Could you attach your about:support? You'll want to do "copy raw data to clipboard", paste that into a file and attach it here. Thanks.
Comment 4•2 years ago
|
||
It seems like we have figured out this issue in bug 1828587, so your about:support information isn't needed any more. If you are using the Dark Space theme or some other theme with an animated background, you can try disabling it until we fix the issue with Firefox. If you try that and it helps the issue, please let us know in this bug. Thanks.
Description
•