Posted by
Sven Gothel on
Nov 07, 2012; 3:00am
URL: https://forum.jogamp.org/Thread-blocking-issue-with-AWT-but-not-NEWT-on-OSX-tp4026674p4026804.html
On 11/07/2012 03:09 AM, ac [via jogamp] wrote:
> is the upcoming fix dealing specifically with the setTitle() call, or anything
> that is called from the frame object? I recall that doing
> frame.setResizeable() also resulted in the application hanging.
Well, I cannot provide a fix to this I am afraid, hence there will be
no upcoming fix as long it's not 'our' fault within JOGL.
You can see in the git commit how I worked around it within
the 2 unit tests - sorry that's all so far.
We have pretty much isolated this issue by now (OSX, after CALayer creation),
but I cannot see us doing anything wrong here causing such a deadlock.
If setResizeable() fails to, I am afraid any mutable frame operation
will deadlock @ 1st init/reshape/display call right after context creation
(1st call).
I tried to remove all locking within our JAWTWindow of OSX,
and also checked locking in our CALayer etc .. but w/ no luck
I could see us blocking OSX's AWT forever.
Well while discussing this w/ you .. we may could workaround
by issuing one NOP display() for OSX to overcome this (?)
Maybe you can try this w/ the JOGL code (unit test, GLDrawableHelper)
if you feel confident.
BTW .. do we have the source code for the OSX Java7 AWT stuff ?
Is it the OpenJDK ? Maybe this will give us a clue whats going wrong.
Would be nice if we can analyze this issue a bit further together.
I know, it's far from being satisfied, but keep in mind the AWT/CALayer
code is new in OpenJDK/Oracle's JRE.
~Sven