Unclear What exactly 'remote thread child' sessions are, and why auto-mem should be skipped for them, is not stated.
What
Several 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()).
Why
This 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.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What exactly 'remote thread child' sessions are, and why auto-mem should be skipped for them, is not stated.