PROBE::VM.OOM_KILL(3stap)

💖 PROBE::VM.OOM_KILL 💖

okay bestie, gather round, because this is a 3stap page from the Memory Tapset and it's lowkey one of the most dramatic probes in the whole tapset. no cap. 🫶

---

✨ NAME ✨

probe::vm.oom_kill — fires when a thread is selected for termination by the OOM killer

like... the kernel literally just picked who's getting eliminated. it's giving survivor but make it memory. 💀

---

🌸 SYNOPSIS 🌸

probe vm.oom_kill {}

that's it. no args, no fuss, she's a simple girl. ✨

---

🎀 VALUES 🎀

these are the lil variables you get to peek at when this probe fires, and honestly? they're the whole plot:

• task — the task being killed 😭 (yes, the actual one getting voted off the island)
• name — name of the probe point 🏷️ (it's just... its name. iconic behaviour, honestly)

---

🦋 CONTEXT 🦋

so here's the vibe check: this probe fires in the context of the process that tried to consume excessive memory, and thus triggered the OOM. 🍓

translation bestie: the culprit. the one who ate all the RAM. the main character who took "treat yourself" a little too literally and now everyone's paying for it. not me side-eyeing the memory hog 🙈

---

🔥 SEE ALSO 🔥

• tapset::memory(3stap) — go read the memory tapset page, iykyk 💅

---

and that's the whole page, you ate that ✨👑

this has been the SystemTap Tapset Reference, and the date on it is September 2026 — so yeah, freshly dated, cute, and ready for you. bye bestie, go read tapset::memory(3stap) next! 💖🎀🦋🌈⭐