MacOS 10.9.2 Newt test giving me busy spinner and unresponsive window

I'm trying to nail down why I'm getting a busy spinner and an unresponsive window in my simple test:

Foo.java

I added the console output in the display method just to make sure it was being called by the animator but I get the busy issue with or without it.

A little about my environment:
MacOS 10.9.2
Java build 1.7.0_51-b13

jogamp-all-platforms/jogl.artifact.properties:
gluegen.build.version=2.1.5
gluegen.build.number=779
gluegen.build.id=2014-03-10_14-59-56
gluegen.build.branch=origin/master
gluegen.build.commit=6476552f46c7bc7b151d53a9e8d2332deda10fcb
jogl.build.version=2.1.5
jogl.build.number=1240
jogl.build.id=2014-03-11_04-15-42
jogl.build.branch=origin/master
jogl.build.commit=ba0dc6462a88ee7512a087deaaca760239915548

My compile and run:
javac -cp ".:jogamp-all-platforms/jar/gluegen-rt.jar:jogamp-all-platforms/jar/jogl-all-noawt.jar" Foo.java
java -cp ".:jogamp-all-platforms/jar/gluegen-rt.jar:jogamp-all-platforms/jar/jogl-all-noawt.jar" Foo

At this point I'm pretty stumped.

EDIT:
I have also attached a debug log using:
-Dnewt.debug=all -Dnativewindow.debug=all -Djogl.debug=all
to see if that gives some info to help.
Foo.log

On 03/22/2014 11:00 PM, Moth [via jogamp] wrote: Nothing 'special' in your code .. hmm,
do our test applets work on your platform ?

Pls open a bug report and attach your code, test.log and test_dbg.log
      etc/test.sh >& test.log
      etc/test_dbg.sh >& test_dbg.log

See FAQ/Bugreport.

Something odd for sure .. sorry.

~Sven

https://jogamp.org/bugzilla/show_bug.cgi?id=1001

Thanks for looking in to this.

I have started to see similsr reports for about all projects shipping native code for macosx.

The Oracle JVM in 7 and 8 has removed support for the .jnilib library format. We need to rebuild all native libraries for mac os x using the .dylib format.2014-03-23 08:45 skrev Moth [via jogamp]:
https://jogamp.org/bugzilla/show_bug.cgi?id=1001

Thanks for looking in to this.



If you reply to this email, your message will be added to the discussion below: http://forum.jogamp.org/MacOS-10-9-2-Newt-test-giving-me-busy-spinner-and-unresponsive-window-tp4032038p4032041.html
To start a new topic under jogl, email [hidden email]
To unsubscribe from jogamp, click here.
NAML

I can not reproduce the problem. I used other JAR-files (jogl-all instead of jogl-all-noawt) maybe that is an explanation, here is my setup.

OS X 10.9.2 (13C64)
Java(TM) SE Runtime Environment (build 1.8.0-b132)

GLUEGEN_RT=.m2/repository/org/jogamp/gluegen/gluegen-rt/2.1.5-01/gluegen-rt-2.1.5-01.jar
JOGL_ALL=.m2/repository/org/jogamp/jogl/jogl-all/2.1.5-01/jogl-all-2.1.5-01.jar

javac -cp "$GLUEGEN_RT:$JOGL_ALL" Foo.java
java -cp "$GLUEGEN_RT:$JOGL_ALL:." Foo

I see the window (and can move/resize), the triangle and the console gets a lot of "Foo.display"

Interesting.  I just tried this too and the issue stops.  I thought to use Newt on it's own you needed to use jogl-all-noawt.jar.  Is that not the case?  If I run against jogl-all.jar is my code using AWT or Newt for the display and event handling?

On 03/23/2014 08:58 AM, Xerxes Rånby [via jogamp] wrote:
> I have started to see similsr reports for about all projects shipping native
> code for macosx.
>
> The Oracle JVM in 7 and 8 has removed support for the .jnilib library format.
> We need to rebuild all native libraries for mac os x using the .dylib

I don't think so, since we load the native libraries w/ full path spec,
hence can have any extension/suffix.

~Sven

On 03/23/2014 06:48 PM, Moth [via jogamp] wrote:
> Interesting.  I just tried this too and the issue stops.  

Pls elaborate when this 'issue' still exist
and pls update the bugreport 1001 accordingly.

(1001 - a fairy tale number)

> I thought to use
> Newt on it's own you needed to use jogl-all-noawt.jar.  Is that not the case?
>  If I run against jogl-all.jar is my code using AWT or Newt for the display
> and event handling?

jogl-all: means all, i.e. including NEWT and AWT
jogl-all-noawt: means all but AWT, i.e. includes NEWT but not AWT.

~Sven

On 03/24/2014 07:57 AM, Sven Gothel wrote:
> On 03/23/2014 06:48 PM, Moth [via jogamp] wrote:
>> Interesting.  I just tried this too and the issue stops.  
>
> Pls elaborate when this 'issue' still exist
> and pls update the bugreport 1001 accordingly.

Sorry I saw that you updated the entry already ..

Lets cont. discussion there to avoid duplication.