Does anybody know why we use awtLock for soo long time in the toolkit
loop? Especially why we call dispatchEvent() under this lock?
On 02.10.2013 1:03, Anthony Petrov wrote:
The fix looks fine to me.
--
best regards,
Anthony
On 10/01/2013 06:35 PM, Alexander Zvegintsev wrote:
Hello,
Could you please review a fix for following issues:
https://bugs.openjdk.java.net/browse/JDK-7158311
https://bugs.openjdk.java.net/browse/JDK-8001463
webrev:
http://cr.openjdk.java.net/~serb/alexz/7158311/webrev.00/
All X11 implementations of DisplayChangedListener does not call any X11
routines, hence
SunGraphicsEnvironment.displayChanged() callback does not require an
AWTLock and we
can temporarily release it to avoid deadlock.
--
Best regards, Sergey.
