this post was submitted on 03 Nov 2024
164 points (100.0% liked)

Linux

5222 readers
122 users here now

A community for everything relating to the linux operating system

Also check out !linux_memes@programming.dev

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] FizzyOrange@programming.dev 12 points 1 week ago (2 children)

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.

[–] ObsidianZed@lemmy.world 3 points 1 week ago (1 children)

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.

[–] FizzyOrange@programming.dev 3 points 1 week ago

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?