{"version":"2.1.246","anchor":"late-attach-release-and-oom-kill-accounting-for-capped-proce","canonical_anchor":"late-attach-release-and-oom-kill-accounting-for-capped-proce","heading":"Late attach, release and OOM-kill accounting for capped processes","tier":"soon","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/late-attach-release-and-oom-kill-accounting-for-capped-proce","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Late attach, release and OOM-kill accounting for capped processes\n\nCapped processes can be attached late, released, and have their out-of-memory kills counted; still off.\n\n**What**\n\nProcesses started before the memory cap is decided are parked and attached later along with their children, a process and its descendants can be released back out of the cap, and OOM kills are counted. Same gating as the rest of the tool cgroup work, which is off by default.\n\n**Details**\n\n- The OOM counter is polled from `memory.events` and reported as `oom_kills`, along with `cgroup_v2`, on `tengu_tool_cgroup`.\n- A separate keeper directory holds processes meant to outlive the capped tree.\n\n**Evidence**\n\n`released_count`\n\n- Area: Sandbox\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 0\/5\n- Present in the build but not switched on"}