Well I had thought that PaleMoon/Firefox "had solved the memory leaks". Apparently according to piglet, not exactly.
Can someone explain what the browser is *doing* with all that space? You can go to some random webpage (not even a video) and all of a sudden it spikes!
Well, I will say that I do have a question in regards to PP...
If you look at memory like a series of cells
(with U= in use, and F = free)
And then load a program
Then the program has to do something, i.e. load a tab, that will spike usage for a brief time
And then gives that memory back... though its not contiguous
And then does this a few times without compacting, because nothing else needs the memory currently...
What would PP show in that case? Because that's a lot of the way that memory management in a garbage collected world works. Working Set is the current size, in bytes, of the Working Set of this process. The Working Set is the set of memory pages touched recently by the threads in the process. If free memory in the computer is above a threshold, pages are left in the Working Set of a process even if they are not in use. When free memory falls below a threshold, pages are trimmed from Working Sets. If they are needed they will then be soft-faulted back into the Working Set before leaving main memory.
Is the memory being reported the WS Private or the WS Sharable?
A good explanation that goes into it better than I can: http://cybernetnews....ory-usage-explained/