{"version":"2.1.232","anchor":"more-globals-moved-behind-per-host-lazy-instances","canonical_anchor":"more-globals-moved-behind-per-host-lazy-instances","heading":"More globals moved behind per-host lazy instances","tier":"internal","area":"Session State","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/more-globals-moved-behind-per-host-lazy-instances","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### More globals moved behind per-host lazy instances\n\nPer-host lazy caches tripled from sixteen to fifty-one, so parallel sessions stay separate.\n\n**What**\n\nThe holder that returns one instance per host, created on first use, went from 16 construction sites in v2.1.231 to 51 here. Two sessions or SDK instances sharing a process no longer share these caches.\n\n**Details**\n\n- Newly host-scoped: the memory-extraction registry, whose extractor and drainer callbacks are installed per host and drained against a 60000 ms timeout, and an IDE-state holder.\n\n**Evidence**\n\n`P8e = Symbol(\"ide-not-yet-computed\");`\n\n- Area: Session State\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}