That’s cool, but in my experience if you get to the OOM killer then 80% of the time it’s too late and your system is basically dead. My laptop hard reboots most of the time when this happens.
99% of the time, it’s my browser, so I ended up writing a script that watches memory used. If it reaches 95%, it throws a warning, and 98% force kills my browser.
I’d rather that happen than my entire system lock up and have to hard reboot.
There’s a “proper” version of this hack called early oom. I haven’t used it though and now that I look at it it seems like it uses the same completely broken “guess which process to kill, who cares if it’s init” system that the normal oom killer uses so your solution sounds better.
Is it so hard to just pause the system and ask the user which app to kill?
That’s cool, but in my experience if you get to the OOM killer then 80% of the time it’s too late and your system is basically dead. My laptop hard reboots most of the time when this happens.
Hopefully it works with the early-OOM hacks.
99% of the time, it’s my browser, so I ended up writing a script that watches memory used. If it reaches 95%, it throws a warning, and 98% force kills my browser. I’d rather that happen than my entire system lock up and have to hard reboot.
There’s a “proper” version of this hack called early oom. I haven’t used it though and now that I look at it it seems like it uses the same completely broken “guess which process to kill, who cares if it’s
init” system that the normal oom killer uses so your solution sounds better.Is it so hard to just pause the system and ask the user which app to kill?