GLCanvas problem with JOGL 2.0 RC4 on OSX Snow Leopard (32-bit VM)

Hi,

I'm upgrading the Agile2D library to JOGL 2.0 RC4 and I'm testing it in many platforms.
When testing it on OSX Snow Leopard 10.6.8, JOGL won't work when using GLCanvas with a 32-bit VM (I've tested it in more than one machine).
I've pasted below the output of the errors when trying to launch the GEARS example.
Note that GLCanvas works fine with a 64-bit VM and GLJPanel works fine with both 32 and 64 VM.

Any ideas?
Thanks in advance!

Rodrigo
(I can post the longer output with debug flags if it may help)

******************
Exception in thread "main-AWTAnimator-1" java.lang.IndexOutOfBoundsException
        at java.nio.Buffer.checkIndex(Buffer.java:518)
        at java.nio.DirectByteBuffer.getLong(DirectByteBuffer.java:760)
        at com.jogamp.common.nio.StructAccessor.getLongAt(StructAccessor.java:169)
        at jogamp.nativewindow.jawt.macosx.JAWT_MacOSXDrawingSurfaceInfo.getCocoaViewRef(JAWT_MacOSXDrawingSurfaceInfo.java:53)
        at jogamp.nativewindow.jawt.macosx.MacOSXJAWTWindow.lockSurfaceImpl(MacOSXJAWTWindow.java:173)
        at jogamp.nativewindow.jawt.JAWTWindow.lockSurface(JAWTWindow.java:278)
        at jogamp.opengl.GLDrawableImpl.lockSurface(GLDrawableImpl.java:195)
        at jogamp.opengl.GLDrawableImpl.setRealized(GLDrawableImpl.java:156)
        at javax.media.opengl.awt.GLCanvas.validateGLDrawable(GLCanvas.java:573)
        at javax.media.opengl.awt.GLCanvas.display(GLCanvas.java:394)
        at com.jogamp.opengl.util.AWTAnimatorImpl.display(AWTAnimatorImpl.java:74)
        at com.jogamp.opengl.util.AnimatorBase.display(AnimatorBase.java:142)
        at com.jogamp.opengl.util.Animator$MainLoop.run(Animator.java:176)
        at java.lang.Thread.run(Thread.java:680)
Invalid memory access of location 0x15c eip=0x371c63
Bus error

On Wednesday, December 14, 2011 03:40:16 PM andrade [via jogamp] wrote:
Thank you.

Can you file a bugreport on https://jogamp.org/bugzilla/ ?

I work on fixes for OS X these days anyways, hence I hope I can add this one
to my list.

Is there a use case for the 32bit JVM on OS X ?

~Sven

> Can you file a bugreport on https://jogamp.org/bugzilla/ ?

Ok, I described it here:
https://jogamp.org/bugzilla/show_bug.cgi?id=536

> I work on fixes for OS X these days anyways, hence I hope I can add this one
> to my list.

Great, thanks! I'll post another crash problem concerning OSX Lion.

> Is there a use case for the 32bit JVM on OS X ?

Not sure if I understand what you mean by "use case"...

Hi

Is the ability to use a 32-bits JVM on a machine with a 64-bits processor really useful? As far as I know, there is the same kind of problem on Windows but it comes from some OpenGL drivers. Maybe GlueGen could detect which kind of VM is used but handling this particular case might be not trivial.

gouessej wrote

Hi

Is the ability to use a 32-bits JVM on a machine with a 64-bits processor really useful? As far as I know, there is the same kind of problem on Windows but it comes from some OpenGL drivers. Maybe GlueGen could detect which kind of VM is used but handling this particular case might be not trivial.

Hi,

I see what you mean, but I've used the 32-bit JVM on a 64-bit processor Mac as a complementary test. Originally, I had tested it on a Mac Book with a 32-bit processor (OSX 10.6) and the problem was the same.

By the way, I've tested it on a Windows 7 32-bits and it works fine.

On Thursday, December 15, 2011 10:19:58 AM andrade [via jogamp] wrote: Yup, we test this one - true.

Looks like I have to enable 32bit JVM testing on OS X as well.

~Sven