Posted by Sven Gothel on Oct 28, 2015; 6:58pm
URL: https://forum.jogamp.org/Issues-with-JOGL-under-OS-X-tp4035608p4035648.html

On 10/27/2015 10:49 AM, agggile [via jogamp] wrote:
> Hey. Thought I'd post this here because I can't put my mind around this issue.
> So, I'm in the midst of reconstructing some extremely old code, and I decided
> to update JOGL. I'm not even sure what sort of JOGL build the old code was
> using. Anyway, I successfully updated the libs to a more recent build. The
> code works with every Windows build I've come across, but for some reason it
> won't function under OS X. Here's a log with debug-all:
>
> http://pastebin.com/raw.php?i=jsa3cAtG

Thank you for the log file, I have to analyze it in detail and compare it,
see below.

However, it seems that general initialization has passed and was successful.

+++

It would be great if you could:

- use the latest Oracle JRE for OSX

- try one of our applets on you machine
  and produce the log file.

  <http://jogamp.org/deployment/jogamp-current/jogl-test-applets.html>

  Also state whether the applets work in general on your machine.

  Best is you can test multiple applets, i.e.
    - one simple one, i.e. Gears
      <http://jogamp.org/deployment/jogamp-current/jogl-applet-runner-newt-gears-normal-napplet.html>

    - one which uses AWT as your applet does,
      look on the bottom of the applet test page
      which include GLCanvas and GLJPanel tests.
      E.g.: <http://jogamp.org/deployment/jogamp-current/jogl-applet-gl2_gljpanel02.html>

- produce the log file w/ the Oracle JRE and your application

- tar+gz/zip the log files and publish them for us.



>
> After that, it's just "NSOpenGLLayer.Attach: Re-Queue, drawableHandle
> 0x7f7fbb02f9a0 - AWT-AppKit" for an additional 3 billion lines, after which I
> dispose of everything and return to the original screen. I'm extremely new to
> OpenGL and JOGL, but I assume there's some sort of information hidden in that
> log. I will provide code from the project when necessary.

It is possible that this issue is somewhat inherent to your application.
Hence we do need all infos as stated above.

~Sven