Login  Register

Re: Thread blocking issue with AWT (but not NEWT) on OSX

Posted by Sven Gothel on Nov 07, 2012; 12:45am
URL: https://forum.jogamp.org/Thread-blocking-issue-with-AWT-but-not-NEWT-on-OSX-tp4026674p4026802.html

On 11/06/2012 11:47 PM, ac [via jogamp] wrote:

> Right, the change that brought the deadlock when calling Frame's methods is
> precisely the first commit of the FBObject, GLFBODrawable integration:
>
> http://jogamp.org/git/?p=jogl.git;a=commit;h=4dd44b985fe0541be3a3bcd9045d201ed3ca2cc5
>
> If I use the commit immediately before:
>
> http://jogamp.org/git/?p=jogl.git;a=commit;h=9036376b7806a5fc61590bf49404eb71830de92f
>
> with my test code, I actually get the following crash originating in the
> native libs, regardless of whether I use frame.setTitle() or not:
>
> 2012-11-06 17:39:32.306 java[36537:12003] invalid drawable
> 2012-11-06 17:39:32.309 java[36537:12003] -[NSView CGLPBufferObj]:
> unrecognized selector sent to instance 0x7fc5f2c998c0
> 2012-11-06 17:39:32.309 java[36537:12003] An uncaught exception was raised
> 2012-11-06 17:39:32.309 java[36537:12003] -[NSView CGLPBufferObj]:
> unrecognized selector sent to instance 0x7fc5f2c998c0
Yup, thats expected, since that bug is fixed in the upcoming commit.

However, culprit of the deadlock is the CWindow._setTitle(..)
implementation itself.

What I only can assume it that the Frame/Window setTitle impl.
somehow gets confused w/ the offscreen JAWT CALayer usage
and hence is a bug in that department.

~Sven


signature.asc (907 bytes) Download Attachment