<AWT Dev> OpenJdk11-28-EA JDialog hanging

Denis Fokin denis.fokin at gmail.com
Fri Oct 26 15:11:48 UTC 2018


Hi guys,

just out of curiosity, should not we store the SE lists per-AppContext?

Thank you,
   Denis

On Fri, Oct 26, 2018 at 1:35 AM Krishna Addepalli <
krishna.addepalli at oracle.com> wrote:

> Hi Sergey,
>
> I also agree with Laurent about root cause of hang provided by Martin.
> However, we just need to make sure that non Sequenced Events are not
> dispatched when SequencedEvents are being dealt with.
>
> Thanks,
> Krishna
>
>
> On 25-Oct-2018, at 1:35 PM, Laurent Bourgès <bourges.laurent at gmail.com>
> wrote:
>
> Hi Sergey & Martin,
>
>
>> > AWT experts, what do you advice about asynchronous events: to Block or
>> to dispatch selected awt events...
>>
>> I think that before answer this question we need to clarify why the
>> current code hangs.
>>
>
> According to me, Martin already exposed his detailled analysis of 2 cases
> making AWT to hang with several AppContexts: in summary, like a deadlock,
> the EDT threads are waiting for each other to dispatch SequencedEvents !
>
> Please Martin correct me, or maybe give us an updated diagnostic of the
> problem ?
>
> This thread is already quite long and both Martin & me invested a lot of
> time on debugging, fixing & testing, please give us your understanding,
> Sergey.
>
> Finally I am in favor of Martin's patch 2 sent by Oct 16th:
> http://cr.openjdk.java.net/~mbalao/webrevs/8204142/8204142.webrev.02
>
> Cheers,
> Laurent
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/awt-dev/attachments/20181026/97a17ca7/attachment.html>


More information about the awt-dev mailing list