If you prefer not to open a bug, you can instead reduce the number of content processes used by Firefox to a lower amount by going to about:config and changing dom.ipc.processCount.webIsolated to a lower number.
If you want to find the bug, you can run a mozregression to find what broke it (using 114 as your last known good release and 115 as your bad release).
Please reach out if you need help with this.
You can use your profile to test this pretty easily.
If Firefox is using an unexpected amount of RAM, report a bug by following the steps below:
about:memoryin a new tab.about:supportinfo (Click Copy text to clipboard) to your bug.If you prefer not to open a bug, you can instead reduce the number of content processes used by Firefox to a lower amount by going to
about:configand changingdom.ipc.processCount.webIsolatedto a lower number.You could always disable hardware video decode acceleration and continue to watch videos.
Please report issues: https://firefox-source-docs.mozilla.org/performance/reporting_a_performance_problem.html
I just compared the behavior in both Chromium and Firefox on my machine, and as far as I can tell, they act the same.
Steps to reproduce:
What happens:
The buffer is cleared in both browsers.
What are you seeing that is different?
If you want to find the bug, you can run a mozregression to find what broke it (using 114 as your last known good release and 115 as your bad release).
Please reach out if you need help with this.
You can use your profile to test this pretty easily.