I’m surprised how many people bring up “Erm that memory is actually not being used” as if there isn’t plenty of knock on effects from how memory pressure is actually done. For example, if I keep chrome open long enough my builds slowly use less and less threads because the build thinks there’s less memory available, so I have to periodically close chrome and reopen and restore last session.
It’s true reported memory allocation does not equal actual memory used and that’s very clever of everyone who brings it up, but it does actually cause real annoyances.
>so I have to periodically close chrome and reopen and restore last session.
I thought ublock was forced out of Chrome months ago... how are you people still using it? I switched back to Firefox a couple years ago already, even if it's occasionally painful.
Yeah I actually use Firefox almost exclusively, I only use Chrome when websites mysteriously don't work in firefox, 99% of the it's lack of firefox support.
But in my example I was thinking of a particular 2-month stretch where this kept biting me and I was using Chrome at that point. In terms of memory usage, Firefox is no better though (at one point it was, but not any more).
Now I'm afraid of saying "memory usage" lest someone pops out to comment "that's not how memory works" like whack-a-mole.
It’s true reported memory allocation does not equal actual memory used and that’s very clever of everyone who brings it up, but it does actually cause real annoyances.