{"version":"2.1.246","anchor":"stale-session-cleanup-no-longer-confuses-process-ids-from-di","canonical_anchor":"stale-session-cleanup-no-longer-confuses-process-ids-from-di","heading":"Stale-session cleanup no longer confuses process ids from different containers","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/stale-session-cleanup-no-longer-confuses-process-ids-from-di","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Stale-session cleanup no longer confuses process ids from different containers\n\nSession cleanup now tracks which machine a process belongs to, so container ids stop colliding.\n\n**What**\n\nEach registered session now records which machine and process namespace its process id belongs to, and the sweep that clears out dead sessions skips any entry recorded elsewhere. Previously a process id from another container could match a live local process and be misread.\n\n**Details**\n\n- On Linux and WSL the identifier is derived from `\/etc\/machine-id` plus `\/proc\/self\/ns\/pid`; other platforms use a fixed value.\n- Both the session key files and the pid files are checked this way.\n- Windows container environments skip the registry sweep entirely, detected by `CONTAINER_SANDBOX_MOUNT_POINT` being set or `USERNAME` being `ContainerAdministrator` or `ContainerUser`.\n\n**Evidence**\n\n`pidDomain: await Yo(),`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}