Memory leak on GPU process in Firefox 87.0
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
People
(Reporter: ricothecat1, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:87.0) Gecko/20100101 Firefox/87.0
Steps to reproduce:
The GPU process is not releasing RAM to the system.
The problem is more severe when i try to watch HTML5 video on Youtube and i switch 4 - 5 videos in rapid succesion.
The GPU process skyrockets and even when i closte the tab where the video was played the GPU process is still using approx 1 GB of RAM.
I have tried to start Firefox without extensions (i use 1. uBlock Origin) and even tried to update my GPU drivers. The last thing i have tried is to perform clean instalation of Firefox and even then the problem with GPU process not releasing memory prevails.
Also i have discovered that on a multiple GPU systems (systems Equiped with Nvidia Optimus technology) there is a problem with Firefox not switching the GPU in the event of change by user (for example some laptops are designed to switch the OS to the low power GPU), the Firefox is still using the dedicated GPU and is passin thru the image using dwm.exe (Desktop Window Manager) and causing it to consume memory. If this happend only once during switch it would be ok but the Firefox is causing the dwm.exe to consume memory with each HTML5 wideo playback or even with each switch of the tabs in the open window.
Actual results:
GPU process of the Firefox 87 is not releasing unneded memory to the system.
Filrefox don't switch GPUs based on the system demand.
Expected results:
The memory management of the GPU process should be optimized.
The GPUs should switch based on the system demands thus not hinder the system by using dwm.exe to pass the data from one GPU to the other and causing it to consume more meory
Comment 1•4 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 revert this change in case you think the bot is wrong.
Updated•4 years ago
|
Updated•4 years ago
|
Comment 3•4 years ago
|
||
Looks like duplicate of bug #1386177. If you think that it's not, please reopen this bug.
Updated•4 years ago
|
Updated•4 years ago
|
Description
•