What madness this, I tested here now with it open and still Opera together, 5 tabs each, consuming 41% of my RAM, I also have 8GB, this happens only with Firefox?
Only if you are in front of the computer using the browser fairly heavily for hours on end will you notice this. Also, there is a high correlation with the number of tabs in use. THEN, you also have to leave the system in sleep mode rather than turning it off and for a long time...like days or even a few weeks. Anyway, for me it just points to a trend, and I think it suggests that browser devs can and I feel should improve memory management of their apps. I sense just a little bit of sophistication will do the job.
I leave systems in stand by rather than turn them off...been a habit for I guess 15 years. I have really noticed "RAM creep" since about 2012, when the hardware made for me using the internet worth spending many hours searching and chronicling information. Over the course of a long boot, say 15-20 days, I began noticing that system RAM would always rise with the browser leading the way. I say this, because any "RAM creep" happening without use of a browser is extremely minimal. Well, as my use of browsers has gone up, now I notice it takes almost exactly 8 days for Chrome to freeze Windows. Literally, this same pattern has repeated itself over and over many many times. Again, this is very heavy testing, and the PC isn't even in sleep mode. It's fully on 24/7 with video running while I have been doing this. With testing, I guess I have been at it hard for the last 3 months and off and on for about a year or a little bit more. My interest in this topic goes way back though, all the way to Windows 98.
My experience as well. Quantum is much better than prior versions, but it still has problems. Back 20 or 30 versions ago FF was PATHETIC in terms of Memory leaking. (But then, so was Chrome.)
I too have 8 GB and I do not intend for FF to burn up 80 % of it. Period. It does help to periodically restart it. But then rebooting every so often does as well.
FWIW, I don't use FireMin much on this machine (Win 7 pro 64) **. On an old XP 2 GB box I always run it with FF and derivatives. Otherwise, memory gets melted by FF. Note that FireMin is one of the few type memory programs that actually works and are not snake oil.
** On this box I usually run Process Lasso and it has some good memory management built in.
Thanks for the information. I'd like to try FireMin, and maybe I will. These apps can be scary in that I have seen and heard of many bad extensions floating around. I installed an extension that claimed to be anti-miner. I think it actually contained eternal blue itself, and I had the feeling that something really creepy was happening in memory. Don't recall exactly what happened but it seems the internet went out on another connected PC here. That was enough for me, since miner malware uses eternal blue double pulsar with its ability to spread across a network. Systems were patched here anyway, but I don't like the trend in that malware.
Obviously, I got rid of the extension, and I don't think anything was written from memory to disk. Comodo would have told me if it tried. Seemed to me like maybe it was something of a miner itself that would run only when the browser was open (running with FFs trust in the security software), rather than attempt to install anything or make any changes to the system. After I rebooted and ran for awhile, I felt like the strangeness was gone. Creeped me out though.
100% your experience and mine are the same when it comes to restarting FF, although as the starting point of system memory usage is concerned, I notice each new FF session leaves the system memory at a higher point when FF is then closed. Rebooting is the sure fire fix...LOL or crash FF and use the crash reporter.
Funny thing, going way back. I remember being happy to see the crash reporter in FF even way back in like FF 3.6. Seems it has always had a crazy ability to dump RAM. In those days, I was looking at silly RAM optimizers occasionally. None of them worked, o/c. Sounds like you are familiar also with the topic...RAM Rush, RAM Boost, etc.
BTW, I like CleanMem and use it here. I read up on the app, and it seems to help with some things. However, I think it may lack the ability to do hard core trimming. Trimming to standby levels seems to have a decreasing payoff over time, although a good practice. Anyway, I still feel the browser writers will end up conquering the worst of this issue, based on what I have seen in FF 57. Chrome is a little bit better on RAM I think at this point, but FF seems to know it should fight as system memory climbs. Meanwhile, Chrome is moreso simply lacking any sort of native sophistication for managing high system-wide memory usage (contributing to managed system memory use)...full speed into the wall...