On Fri, 29 Jan 2021 04:03:29 GMT, Prasanta Sadhukhan <psadhuk...@openjdk.org> wrote:
> It seems "m_breakMessageLoop" is never true for unsuccessful run even though > AwtToolkit::QuitMessageLoop finish execution (where m_breakMessageLoop is set > to true), > so AwtToolkit::MessageLoop never ends and shutdown hook gets called where > tk.isDisposed() loop start spinning. seems to be some timing issue. Then this does look like a synchronisation problem. One thread changes the value of `m_breakMessageLoop` but another doesn't see it's changed. Should `m_breakMessageLoop` be declared as `volatile`? ------------- PR: https://git.openjdk.java.net/jdk/pull/2220
