Wesley Moore on Nostr: In the history of time has the #Linux OOM killer ever picked a sensible process? 8Gb ...

In the history of time has the #Linux OOM killer ever picked a sensible process? 8Gb Rust Rover process sitting right there, but nope the 6.8Mb user dbus-broker looks like a better target, lets kill that and end my entire session.

(I tried messing with `vm.overcommit_memory` and `vm.overcommit_ratio` a while back but large amounts of RAM got wasted/things reported OOM while there was plenty of free-RAM—the reason for overcommit alas)