Ramin Honary 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.

nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqvr4dqq5vzpz0kaavv3lc3098jmfzrpdtj79dazpemytqw4ansf0qkv5f2h (nprofile…5f2h) I know nothing about memory tuning on Linux, but is there really no way to configure the OOM killer algorithm to just choose the process with the largest footprint?