Here is a link to one of the bug reports: https://bugzilla.mozilla.org/show_bug.cgi?id=1897006

Said report was closed down and presumed “fixed” but I still encounter this issue on the latest stable.

When you know what to search for you’ll find numerous users reporting similar behaviour on Reddit and other social platforms going back multiple years.

If I were more invested I would keep submitting bug reports and memory dumps in the hopes that it may once and for all get stomped. But I’ve made the leap back to chromium and can’t justify the time. I realise that this is a major issue but one that only affects a small percentage of users, likely affecting specific hardware / setups. If the developers aren’t able to reproduce it then it’ll probably remain unfixed.

I ditched Firefox due to a vicious memory leak which was so hard to track down (didn’t register in task manager) that I reinstalled windows before finding the culprit. As soon as I identified Firefox as the cause and then, when I knew what to search for, discovered it was a known bug existing for years I ditched the browser with prejudice.

I need more of these juice based comic strips! :D