A few ideas to explore if you have the time: * Try turning on the pref gfx.webrender.compositor.force-enabled in the about:config page - this may directly fix the issue but it may cause flickering issues when a browser window is on the border between monitors on nvidia drivers if a high refresh rate monitor is present (we currently disable the compositor to keep this flickering from occuring on affected systems with an nvidia gpu and high refresh rate and regular refresh rate monitors side by side, but not using the compositor can cause video playback code to behave very differently any might be at the heart of this memory issue). * Try installing Firefox Nightly - it is two major versions ahead of the current stable and if we happen to have fixed something in that time range it would be good to confirm (and it would give you a workaround of sorts as you can sync your account in Nightly to your regular release channel browser if you wish). * Try [mozregression](https://mozilla.github.io/mozregression/) if you have a few hours to spend on this issue - it runs several different versions of Firefox with a temporary profile (i.e. don't expect it to stick around, it's not going to touch your regular browser experience) and prompts you to reproduce the issue in each and tell it whether the issue is present ('bad') or works fine ('good'), it would then tell you exactly which date and time the firefox code changes happened that broke this for you. Knowing this date and time when things broke would let us immediately fix the issue. If I am able to repro this issue I would be following these same steps to figure out what is going on, but I have not been able to reproduce it yet, so your help is much appreciated if you wish to spend the time :)
Bug 1828587 Comment 67 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
A few ideas to explore if you have the time: * Try turning on the pref gfx.webrender.compositor.force-enabled in the about:config page - this may directly fix the issue but it may cause flickering issues when a browser window is on the border between monitors on nvidia drivers if a high refresh rate monitor is present (we currently disable the compositor to keep this flickering from occuring on affected systems with an nvidia gpu and high refresh rate and regular refresh rate monitors side by side, but not using the compositor can cause video playback code to behave very differently, which might be at the heart of this memory issue). * Try installing Firefox Nightly - it is two major versions ahead of the current stable and if we happen to have fixed something in that time range it would be good to confirm (and it would give you a workaround of sorts as you can sync your account in Nightly to your regular release channel browser if you wish). * Try [mozregression](https://mozilla.github.io/mozregression/) if you have a few hours to spend on this issue - it runs several different versions of Firefox with a temporary profile (i.e. don't expect it to stick around, it's not going to touch your regular browser experience) and prompts you to reproduce the issue in each and tell it whether the issue is present ('bad') or works fine ('good'), it would then tell you exactly which date and time the firefox code changes happened that broke this for you. Knowing this date and time when things broke would let us immediately fix the issue. If I am able to repro this issue I would be following these same steps to figure out what is going on, but I have not been able to reproduce it yet, so your help is much appreciated if you wish to spend the time :)