diff options
| author | Sven Gothel <[email protected]> | 2013-06-24 15:50:27 +0200 |
|---|---|---|
| committer | Sven Gothel <[email protected]> | 2013-06-24 15:50:27 +0200 |
| commit | 8f3b2a4cc14be60681a7bfae0507655cc5702836 (patch) | |
| tree | 2de704ed3f51fe73620e8f38c29988caa7bd600c /make/stub_includes/win32 | |
| parent | c27157bf7fa9776b0f212c2ccfcf80c4e734eedc (diff) | |
Workaroung a Java7 AWT EDT/Robot bug: Validate whether AWT-EDT is alive before certain robot ops.
We have experienced that w/o utilizing AWT components, i.e. NEWT tests,
the AWT-EDT 'sometimes' dies.
Performing AWT robot's waitForIdle() in this situation causes a deadlock,
since the call will never complete it's EventQueue.invokeAndWait() call.
While analyzing this issue, we created a test tool whether the the AWT EDT is still alive.
This test issues EventQueue.invokeLater( .. { flag=true; } ); and polls up until 2s
for the result.
Turns out that the sporadic AWT-EDT issues are solved by this test itself,
i.e. it probably cause it to be reinstated. (?!)
We have to observe this behavior.
Another proof that quantum mechanic rules also apply in the macro cosmos :)
Diffstat (limited to 'make/stub_includes/win32')
0 files changed, 0 insertions, 0 deletions