<div dir="ltr"><div dir="ltr">Hi Krishna,<br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 17, 2018 at 3:51 PM, Krishna Addepalli <span dir="ltr"><<a href="mailto:krishna.addepalli@oracle.com" target="_blank">krishna.addepalli@oracle.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang="EN-US"><div class="gmail-m_8223582111408911367WordSection1"><p class="gmail-m_8223582111408911367MsoListParagraph"><u></u><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><span>1.<span style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:"Times New Roman"">      </span></span></span><u></u><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">This problem (including the one described in JDK-8152974) is not reproducible at all in Mac. I would like to understand why this happens only on Windows/Linux because the proposed fix is in generic code.</span></p></div></div></blockquote><div>Have you tried Laurent's test case on Mac? (the version previous to my refactorings, so we eliminate the OS layer). This bug should manifest there too. Unfortunately, I don't have such environment to test and debug. </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang="EN-US"><div class="gmail-m_8223582111408911367WordSection1"><p class="gmail-m_8223582111408911367MsoListParagraph"><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><u></u><u></u></span></p><p class="gmail-m_8223582111408911367MsoListParagraph"><u></u><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)"><span>2.<span style="font-style:normal;font-variant:normal;font-weight:normal;font-stretch:normal;font-size:7pt;line-height:normal;font-family:"Times New Roman"">      </span></span></span><u></u><span style="font-size:11pt;font-family:Calibri,sans-serif;color:rgb(31,73,125)">I’m not sure if I agree to your proposal of dispatching non-SequencedEvents, from the queue. The events arriving after a particular SequencedEvent could be dependent on this event – for example, the current SequencedEvent could be a focus change event, and the subsequent events could be Key events. So, as per your solution, if we dispatch them, there is a possibility that the intended component may not receive those events.</span></p></div></div></blockquote><div>My understanding is that if you want hard-dependency enforcements, you have to wrap events under SequencedEvent events. All other asynchronous events have absolutely no guarantees. Blocking the EDT should not be done and that's the reason why we dispatch non-SequencedEvent events in the meanwhile. Please note that the only events that are put on hold and re-posted lated are SequencedEvent events that, if dispatched, would violate the sequence rule.</div><div><br></div><div>Kind regards,</div><div>Martin.-</div></div></div></div></div>