OOM-killer not being involked under memory pressure
Hello,
First post to this list, so go easy on me!
Every
few days, my desktop runs out of RAM, and this usually happens while
web browsing. I wait for as much as an hour and a half, but just see
the screen as frozen the way it was at the time of the hang. 8 GB RAM
is installed in it, and it's running Debian 10. My experience with
other Linux distributions has been that the out-of-memory killer works
as expected, but I set vm.oom_kill_allocating_task = 1 in sysctl to
avoid it - yes, I also save the setting persistently in a file
/etc/sysctl.d/60-oom-killer.conf. I'm back to using the default 0
setting. I can reproduce the problem using:
stress -m 4 --vm-bytes 1000M
My
persistent journald logging shows me no evidence of memory pressure
being registered by the kernel or the oom-killer being involved leading
up to the hang, so I'm not sure what to do next.
Pariksheet
Reply to: