<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 5/23/2016 5:00 PM, Sergey Bylokhov
wrote:<br>
</div>
<blockquote
cite="mid:90b4d485-b14a-d3c3-ebb3-dcf467f995de@oracle.com"
type="cite">On 23.05.16 13:29, Semyon Sadetsky wrote:
<br>
<blockquote type="cite">This will not be possible because of
deadlock: the SGE update calls D3D,
<br>
which synchronously send messages to the toolkit thread.
<br>
</blockquote>
<br>
Why it is a problem to call this on the toolkit thread directly?
<br>
</blockquote>
This is how D3D calls are run : sun.java2d.d3d.
<meta http-equiv="content-type" content="text/html; charset=utf-8">
D3DRenderQueue#flashBuffer uses
<meta http-equiv="content-type" content="text/html; charset=utf-8">
AwtToolkit::GetInstance().InvokeFunction().<br>
<br>
--Semyon<br>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<blockquote
cite="mid:90b4d485-b14a-d3c3-ebb3-dcf467f995de@oracle.com"
type="cite">
<br>
<blockquote type="cite">
<blockquote type="cite">I think that XToolkit and LWToolkit
should uses this logic already.
<br>
</blockquote>
On Windows communication with the graphics pipeline is designed
differently.
<br>
</blockquote>
<br>
They are quite similar if not identical. I suggest to check two
solutions:
<br>
- displayChanged is on toolkit thread, only listeners which can
call users code executed on EDT.
<br>
- The main logic on the toolkit thread all listeners are on
related EDT(in this case we will need to save the appcontext of
the listener on addDisplayChangedListener()).
<br>
<br>
<blockquote type="cite">
<br>
--Semyon
<br>
<blockquote type="cite">
<br>
On 29.04.16 9:56, Semyon Sadetsky wrote:
<br>
<blockquote type="cite">Hello,
<br>
<br>
Please review fix for JDK9:
<br>
<br>
bug: <a class="moz-txt-link-freetext" href="https://bugs.openjdk.java.net/browse/JDK-8061637">https://bugs.openjdk.java.net/browse/JDK-8061637</a>
<br>
webrev:
<a class="moz-txt-link-freetext" href="http://cr.openjdk.java.net/~ssadetsky/8061637/webrev.00/">http://cr.openjdk.java.net/~ssadetsky/8061637/webrev.00/</a>
<br>
<br>
Display reconfiguration notification is skipped by JavaWS
and the plugin
<br>
under Windows.
<br>
This happens because native display change event is
scheduled to the
<br>
main app context EDT but the last was disabled by 8004584.
As result NPE
<br>
is thrown on the Toolkit thread and event handling is not
scheduled.
<br>
The fix solution runs display event handling in a new thread
if the
<br>
system EDT is not available.
<br>
Test would require to write native code so the bug is
labeled
<br>
noreg-hard.
<br>
<br>
--Semyon
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
</body>
</html>