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)
Wesley Moore /
npub1f7…efyr8
2025-01-21 04:56:58
Author Public Key
npub1f7lh9a8j8pfcsmch67za4czqj4l3fxcsz5jwm5p0350h8drdvp8ssefyr8Seen on
wss://relay.nostr.bandPublished at
2025-01-21 04:56:58Event JSON
{
"id": "c9e7c26f41610530641235b8b2f408fb130e5aae26bdab9fa5e43fe915288d40",
"pubkey": "4fbf72f4f23853886f17d785dae040957f149b101524edd02f8d1f73b46d604f",
"created_at": 1737435418,
"kind": 1,
"tags": [
[
"t",
"linux"
],
[
"proxy",
"https://mastodon.decentralised.social/users/wezm/statuses/113864567593732078",
"activitypub"
]
],
"content": "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. \n\n(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)",
"sig": "60f181a1358c650ffdc7aad8448291b1bd2e4489992189aac0760be2b64c4d90aafc4ad45aa81deb3dfe786d76c0a52d130d85833c85156e1b1520f729a796b9"
}