SFAIK, we've not had any other reports of this. Perhaps the JDK used by
JB IDE has some other changes too ?
But aside from waiting forever to be questionable (I would guess that a
few seconds is more reasonable),
why would the state change never happens / gets lost ?
The code wants a specific state (NORMAL). What if the window is
transitioned to some other state instead ?
So there's a couple of possibilities.
-phil.
On 1/28/25 10:58 AM, Laurent Bourgès wrote:
Hi aleksei,
I will investigate tonight with openjdk 21.0.6 vs jbr21 but this kind
of lock.wait() looks like a hammer to be kicked later as I am fixing
few freezes in JB IDEs...
I will diagnose what is causing me problems here asap.
Laurent
Le mar. 28 janv. 2025, 18:18, Aleksei Ivanov
<alexey.iva...@oracle.com> a écrit :
Hi Laurent,
I don't think it was reviewed because the backport was clean:
https://github.com/openjdk/jdk21u-dev/pull/965
The “discussion” thread:
https://mail.openjdk.org/pipermail/jdk-updates-dev/2024-September/037274.html
The original changeset was reviewed by client-libs reviewers:
https://github.com/openjdk/jdk/pull/14226
Is the problem reproducible with Oracle JDK 21.0.6? Is it
reproducible
with mainline?
On 2025-01-28 16:14, Laurent Bourgès wrote:
> Hi,
>
> I figured out yesterday that this fix was backported in
jdk21.0.6 and
> it causes freezes...
>
> https://bugs.openjdk.org/browse/JDK-8296972
>
> I did not see any client-libs reviewer as mandatory for awt changes.
> How was it reviewed ?
>
> Cheers,
> Laurent
--
Regards,
Alexey
