<AWT Dev> OpenJdk11-28-EA JDialog hanging
mbalao at redhat.com
Wed Oct 31 16:03:17 UTC 2018
Your MultipleContextsUnitTest test has 2 assertions that don't look good to
* dispatchSENumber < num1
* dispatchSENumber < num2
My understanding is that these assertions mean that a non-SequencedEvent
event is expected to be synchronized with SequencedEvent events. If such
synchronization is needed, the event has to be wrapped in a SequencedEvent
event. There are no guarantees otherwise; previous to my proposal these
event were discarded and in my Webrev.02 they are dispatched asynchronously.
I've tried your test -without these assertions- against my Webrev.02 and it
passes, as well as Laurent's 1st and 2nd test.
On Mon, Oct 29, 2018 at 3:06 PM, Sergey Bylokhov <Sergey.Bylokhov at oracle.com
> Hi, Martin.
> Thank you for this details description of the problem, I have tried to
> summarize it in this test, which should fail on all platforms:
> It creates a number of SequencedEvents and post them in a different
> orders. It also has some additional checks, for example InvocationEvent
> posted in between of SequencedEvents should be dispatched in the same order
> as posted/ or posted not early that SequencedEvents. Some new checks might
> be added.
> Here is another version of the fix which tries to resolve the problem
> covered by the test above:
> But I have run it for a night in a bash loop, and it failed after 100+
> iterations. So there is some room for improvements.
> Note that this fix should be applied on top of JDK-8211435:
> On 26/10/2018 15:25, Martin Balao wrote:
>> If you are talking about an example from this message:
>> 014426.html <http://mail.openjdk.java.net/pipermail/awt-dev/2018-October
>> That's only the first half of this issue, which is indeed easy to fix by
>> just dispatching SentEvent events. The second half is here:
> Best regards, Sergey.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the awt-dev