Re: Linux doesn't seem to manage memory very well

On 2024-05-04 02:13, Computer Nerd Kev wrote:

Carlos E.R. <robin_listas@es.invalid> wrote:

On 2024-05-03 01:23, Computer Nerd Kev wrote:

>
The OP has noted now that the process that consumes their RAM is
Chrome or Firefox. I've not seen a detailed description of why it
happens, but I've long noted that Firefox seems to expand its RAM
usage to the available space, but different from a memory leak in
that it usually leaves a certain amount free. I assume that this
in intended behaviour. I run current Firefox on a PC with 2GB RAM
and I don't have it getting killed by the kernel, nor do I have
problems with kernel crashes/reboots. I've also tried running
recent Firefox on a PC with 512MB RAM and noticed that it performs
much worse than with 2GB RAM, slowing down to a crawl while loading
some websites, suggesting that it really does need more RAM in that
case.

>
Firefox uses a lot of memory.
>
One problem is memory fragmentation. It reserves many chunks then
eventually frees many, but they may not being contiguous, so maybe they
can not be reused, so it requests more memory.

 It seems to me like it looks at the available RAM (not including
swap space) and only works at freeing space when the free RAM
remaining gets to a certain size/percentage. Increading RAM because
one feels there isn't enough space free therefore isn't really a
solution because Firefox will eventually expand to fill that new
space too. Although if it tries to leave a minimum percentage free,
the size of that minimum would increase.
 But it would be great to see an explanation of how it really works
from one of the Firefox developers (one can dream).

If memory serves, my explanation above comes from a Chrome dev, distorted through years of retelling it ;-)
...
--
Cheers, Carlos.