RFR: 8369306: Implement invokeAndWait and finishTerminating on headless platform [v3]

[Kevin Rushforth]

On Mon, 13 Oct 2025 16:10:39 GMT, Andy Goryachev <angorya at openjdk.org> wrote:

>> Can you elaborate on this? What usecase do you see where 2 threads might see different values, leading to problems that could not occur if active was volatile?
>
> generally speaking, when two threads modify a single boolean variable, there might be scenarios, depending on the exact hardware, when the other thread does not see the modified value right away.
> 
> some of the comments in 
> 
> https://stackoverflow.com/questions/65037547/the-volatile-keyword-and-cpu-cache-coherence-protocol
> https://stackoverflow.com/questions/106591/what-is-the-volatile-keyword-useful-for
> 
> might explain it better.

Can this variable be accessed by two threads where one of them doesn't synchronize some other way? If so, then Andy has a point.

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

PR Review Comment: https://git.openjdk.org/jfx/pull/1934#discussion_r2426816937