On Wed, 2024-12-11 at 15:50 -0500, Paul M. Foster wrote: > I call this "memory leakage". I don't know if actual code bugs, or > the sloppy way Firefox allocates and frees memory. As far as I know, > all browsers suffer from this. If you find one which doesn't, let us > know.
It's not only memory leaks but also memory fragmentation that will make memory usage grow, which is a lot harder to prevent... And in case of a browser, it's not only the browser itself that can leak memory, but also the JavaScript programs that run on it. I've seen cases where force-reloading (Ctrl+F5) or closing one page that had been loaded in a tab for a while, and then waiting a couple minutes to give the JavaScript engine's garbage collector time to do its job, freed about 8 GiB (!) of RAM afterwards... -- Jan Claeys (please don't CC me when replying to the list)
