[Firefox Nightly, Arch Linux]Memory Usage Increases Over Time
So, I'm trying to watch some F1 with videos running for the broadcast, and multiple PiP for on-board cameras and map/tracker. While doing this I've noticed that my memory usage slowly creeps up until I either refresh all the sites or the PC crashes because too much of the memory is used. When first loading up/refreshing the site(s) and setting up the PiP videos how I want them, I'm at about 3.5GB of RAM usage, however over time it just adds up until the usage is so high that my PC crashes. I have 16GB (15.6GB) of RAM, I once watched it go above 15GB used before the PC finally crashed. Using the AUR package.
すべての返信 (4)
Hi
First of all - wow, that is a great use of multiple picture in picture.
How many PiP windows do you have running when you are doing this?
I believe I've been sticking to 4 PiP windows to fill up my entire second display, as I can't really stretch the videos, while also having the main stream with commentary and stuff on my main display. I think I also tested with just a single PiP window, and if my memory is correct, it still added up, but possibly not as quickly. The season has ended, but I may be able to run some tests with replays at some point if my subscription is still active if that's needed. Haven't tested other sites because I don't personally have much use for it elsewhere, it is a really nice addition in these special cases though.
I think that Firefox would normally only allow one PiP window in a profile.
Are you using multiple profiles to achieve this ?
Does the Firefox Task Manager (about:performance) and about:memory pages show any indication what takes up this memory?
I believe support for multiple PiP windows have been enabled/added in a recent update (nightly build), from what I can see from my laptop right now it seems like it can be enabled under Nightly Experiments, labeled "Multiple Picture-in-Picture Support". If memory serves right it also increased when using only one PiP window to test it, which is why I added this here, I can try to take a look at it again when I have access to my desktop where I had the issue in a few days.