@skylar @Wiz @lonestarr @mischievoustomato That helps. I need to do some testing, I think whats happening is that firefox allocates a GPU decoder process if a tab has a video object in it even if that object isn't playing. So if you have the average yap'n'react amount of tabs open you might have 3-4GB of vram tied up in player objects.