{"version":"2.1.239","anchor":"per-tool-memory-limits-detect-an-outer-cgroup-already-in-pla","canonical_anchor":"per-tool-memory-limits-detect-an-outer-cgroup-already-in-pla","heading":"Per-tool memory limits detect an outer cgroup already in place","tier":"internal","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/per-tool-memory-limits-detect-an-outer-cgroup-already-in-pla","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Per-tool memory limits detect an outer cgroup already in place\n\nOn Linux, a tool already inside another tool's memory group is reported as nested instead of double-limited.\n\n**What**\n\nOn Linux, setting up the memory limit for a tool now notices when the process is already inside another tool's memory group, clears the directory, logs it and reports the setup as nested rather than trying to nest a second limit.\n\n**Details**\n\n- Setup is still guarded by `tengu_tool_memory_cgroup` when no explicit limit has been set.\n- Whether the system uses cgroup v2 is now recorded on the setup state.\n\n**Evidence**\n\n`tool cgroup: covered by an outer tool cgroup`\n\n- Flag `tengu_tool_memory_cgroup`: Off in both readings (read for one account on one subscription tier against v2.1.239; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}