Hello, AWT Team. Please review the fix for the issue: https://bugs.openjdk.java.net/browse/JDK-8025588 The fix is available at: http://cr.openjdk.java.net/~pchelko/8025588/webrev.00/ The CCC request for public API changes was approved: http://ccc.us.oracle.com/8025588
The problem: Is some cases InvocationEvent was deleted from the EventQueue when it's source was disposed. If this InvocationEvent was created by the LWCToolkit.invokeAnWait, it never exited from the nested event loop, so the application frizzed. The solution: Now when the InvocationEvent is removed it's disposed and the invokeAndWait mechanism gets notified and exits the nested event loop. It's impossible to create a regression test here as the issue is very hard to reproduce. With best regards. Petr.
