Under the hood
An abort-tracking object is no longer created in remote session hook setup
What
In the code that wires up remote/thin-client sessions, an object that used to be conditionally created (when a certain internal flag was true) is now never instantiated at all, in both of the relevant session-hook code paths.
Why
Whatever tracking or abort-handling this object provided is no longer active in these remote session paths; the practical effect for users isn't specified.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What the removed object tracked and what effect its removal has isn't stated in the evidence.