{"version":"2.1.239","anchor":"memory-limits-on-linux-notice-when-the-process-is-already-in","canonical_anchor":"memory-limits-on-linux-notice-when-the-process-is-already-in","heading":"Memory limits on Linux notice when the process is already inside a managed group","tier":"internal","area":"Sandbox","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/memory-limits-on-linux-notice-when-the-process-is-already-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Memory limits on Linux notice when the process is already inside a managed group\n\nOn Linux, a process already inside a managed memory group is reported as covered rather than getting a new one.\n\n**What**\n\nThe Linux memory-limit reader now reports \"covered\" when the process's control group path already contains the marker segment it looks for, instead of going on to work out a new group directory to create. Applies to both the older memory-controller layout and the current unified one.\n\n**Evidence**\n\n`\"covered\"`\n\n- Area: Sandbox\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}