There is an OOM kill count in Linux

Elias-Braun wrote: post #3

Gys wrote: post #2

Not mentioned in the post but OOM = Out Of Memory

Thank you, this was my question after reading this : )

The reader should probably also know about the OOM-killer:

https://neo4j.com/developer/kb/linux-out-of-memory-killer/

Re: There is an OOM kill count in Linux

#5

Post by dumbfounder » Sun, Dec 31, 2023, 1:25 PM UTC

Than never?

Re: There is an OOM kill count in Linux

#6

Post by stavros » Sun, Dec 31, 2023, 1:27 PM UTC

dumbfounder wrote: post #5

Than never?

In the order of preference, it goes "now", then "never". Presumably "later" is even later, so if you don't find it now, you'd better never find it.

Re: There is an OOM kill count in Linux

#7

Post by contrarian1234 » Sun, Dec 31, 2023, 1:29 PM UTC

Out of curiosity, what do people recommend for OOM these days on Linux?

My number one recurring issue on Ubuntu is me not noticing the memory usage, running out of memory and locking up my system (forcing a hard reboot and loss of unsaved work)

EDIT: I'd preferably like an OOM handler that would freeze my system and pop up a little menu from which I could select which process to nuke

Re: There is an OOM kill count in Linux

#8

Post by stathibus » Sun, Dec 31, 2023, 1:31 PM UTC

contrarian1234 wrote: post #7

Out of curiosity, what do people recommend for OOM these days on Linux? My number one recurring issue on Ubuntu is me not noticing the memory usage, running out of memory and locking up my system (forcing a hard reboot and loss of unsaved work) EDIT: I'd preferably like an OOM handler that would freeze my system and pop up a little menu from which I could select which process to nuke

early-oom

Re: There is an OOM kill count in Linux

#9

Post by manymatter » Sun, Dec 31, 2023, 1:32 PM UTC

contrarian1234 wrote: post #7

Out of curiosity, what do people recommend for OOM these days on Linux? My number one recurring issue on Ubuntu is me not noticing the memory usage, running out of memory and locking up my system (forcing a hard reboot and loss of unsaved work) EDIT: I'd preferably like an OOM handler that would freeze my system and pop up a little menu from which I could select which process to nuke

I've never had that problem. Maybe you don't setup much swap space as I would expect the system to run well enough to save your work and shutdown for most common leaks.

Re: There is an OOM kill count in Linux

#10

Post by gkbrk » Sun, Dec 31, 2023, 1:35 PM UTC

manymatter wrote: post #9

contrarian1234 wrote: post #7

Out of curiosity, what do people recommend for OOM these days on Linux? My number one recurring issue on Ubuntu is me not noticing the memory usage, running out of memory and locking up my system (forcing a hard reboot and loss of unsaved work) EDIT: I'd preferably like an OOM handler that would freeze my system and pop up a little menu from which I could select which process to nuke

I've never had that problem. Maybe you don't setup much swap space as I would expect the system to run well enough to save your work and shutdown for most common leaks.

Swap usually makes it worse, without swap there is some chance that the Linux OOM killer does something useful and saves the system. With swap, it becomes a frozen system that never manages to kill anything due to all the swapping. You can wait 5 minutes, 10 minutes, or 15 minutes, but the system never recovers without a reboot.