Hi Krishna, I applied the patch on latest OpenJDK12 client and it works well with my reproducer test.
I am really puzzled by this 'One Line' change that seems causing my troubles: ID != SentEvent.ID, so it can explain why AWT was waiting on wrong event ID then hanging for ever ! - edt.pumpEvents(ID, () -> !SequencedEvent.this.isFirstOrDisposed()); + edt.pumpEvents(SentEvent.ID, () -> !SequencedEvent.this.isFirstOrDisposed()); PS: I can no more test with IcedTea-Web as my patch has been merged. Laurent Le mer. 3 oct. 2018 à 14:11, Krishna Addepalli <krishna.addepa...@oracle.com> a écrit : > Hi Laurent, > > > > Sorry, I could not get to the root cause yet. Seems like it might take > some time and some hard debugging. > > > > Meanwhile, I’m attaching a simple patch file which effectively reverts the > earlier fix that was done for JDK-8152974. > > Please try this and let me know if this solves your problem. Then I’ll > create a backout bug and push this patch. > > > > Thanks, > > Krishna > > > > *From:* Laurent Bourgès <bourges.laur...@gmail.com> > *Sent:* Thursday, September 27, 2018 12:57 PM > *To:* Krishna Addepalli <krishna.addepa...@oracle.com> > *Cc:* Phil Race <philip.r...@oracle.com>; Sergey Bylokhov < > sergey.bylok...@oracle.com>; awt-dev@openjdk.java.net > *Subject:* Re: <AWT Dev> OpenJdk11-28-EA JDialog hanging > > > > Any progress on this bug, krishna ? > > > > At least could you explain how SequencedEvent should be processed when > multiple AppContexts are present ? > > > > I could help but I have no clue what's going on ... I observed multiple > several EDT, AppContexts, awt events, it is very complicated to understand > such event handling. > > > > Cheers, > > Laurent > > > > Le jeu. 6 sept. 2018 à 18:02, Laurent Bourgès <bourges.laur...@gmail.com> > a écrit : > > Hi Krishna, > > Le jeu. 6 sept. 2018 à 16:08, Krishna Addepalli < > krishna.addepa...@oracle.com> a écrit : > > Hi Laurent, > > > > Thanks for providing the test case. I was able to reproduce the issue. > Glad to know that you found a workaround, as this issue is a bit tricky to > fix. > > Great. > > > > Meanwhile, I’m looking into fixing this issue, and your test case greatly > helps me toward finding the fix faster. > > > > I tried diagnosing the bug in EDT/SequencedEvent using heap dumps ... but > I got no clues, very tricky. > > > > Good luck, > > Laurent > > > > -- -- Laurent Bourgès
