On Tue, 2 Nov 2021 02:59:44 GMT, Phil Race wrote:
> Any ideas what that fix might have been ?
There were some modifications to the problematic methods in SunToolkit
including JDK-8196100 which would be the reason this test stopped deadlocking
in that particular method.
-
PR: http
On Mon, 1 Nov 2021 15:34:42 GMT, Alexander Zuev wrote:
> Looks like the problem occurs when system is slow to actually close windows,
> then keyboard events are going to the wrong window. The idea of the fix is to
> bring the new window to front before actual testing starts and close window
> on
On Mon, 1 Nov 2021 19:22:02 GMT, Sergey Bylokhov wrote:
> From the stack traces in the bug report, it seems that the problem was in
> some kind of deadlock in the SunToolkit.waitForIdle
I was not able to reproduce the deadlock scenario - and i ran this test about 3
hours non-stop which resulte
On Mon, 1 Nov 2021 15:34:42 GMT, Alexander Zuev wrote:
> Looks like the problem occurs when system is slow to actually close windows,
> then keyboard events are going to the wrong window. The idea of the fix is to
> bring the new window to front before actual testing starts and close window
> on
Looks like the problem occurs when system is slow to actually close windows,
then keyboard events are going to the wrong window. The idea of the fix is to
bring the new window to front before actual testing starts and close window
on EDT and then wait for 2 seconds for actual hardware window to dis
