RFR: 8286830: ~HandshakeState should not touch oops

[David Holmes]

On Fri, 20 May 2022 16:50:19 GMT, Patricio Chilano Mateo <pchilanomate at openjdk.org> wrote:

> But there could still be synchronous operations remaining or about to be added to the queue, again even though the closures won't be executed. In fact we could have some other async operation added to the queue after that

Sorry I'm not clear on the exact details. But a handshake requires the target thread to respond to the handshake request (that is afterall the "handshake" part of it). Once a thread starts to exit it will/should no longer respond to any handshake requests (sync or async) so the submitter of such a request must be polling for the target thread to either acknowledge the handshake or else indicate it is exiting; if the latter then the submitter abandons the handshake request because the target is considered dead. Are you saying that the submitter actually installs the op in the target's queue even if never acknowledged by the target (due to it exiting)?

-------------

PR: https://git.openjdk.java.net/jdk/pull/8795