{"version":"2.1.273","anchor":"auto-mem-and-related-project-features-gain-a-new-is-remote","canonical_anchor":"auto-mem-and-related-project-features-gain-a-new-is-remote","heading":"Auto-mem and related project features gain a new 'is remote thread child' bypass","tier":"internal","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/auto-mem-and-related-project-features-gain-a-new-is-remote","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Auto-mem and related project features gain a new 'is remote thread child' bypass\n\nAuto-mem warm-up and scanning now skip entirely for remote-thread-child sessions\n\n**Unclear.** What exactly 'remote thread child' sessions are, and why auto-mem should be skipped for them, is not stated.\n\n**What**\n\nSeveral call sites that trigger auto-mem warm-up and scanning now add a check that skips this work entirely when the current session is a 'remote thread child' (as determined by a function referred to here as `LU()`).\n\n**Why**\n\nThis avoids running auto-mem warm-up and scanning in sessions spawned as children of a remote thread, where the finding implies it isn't appropriate or needed.\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}