Re: stuck in Processing with with any JOGL release >= RC6 (Mac)
Posted by Sven Gothel on Jul 13, 2012; 10:35am
URL: https://forum.jogamp.org/stuck-in-Processing-with-with-any-JOGL-release-RC6-Mac-tp4025519p4025521.html
On 07/13/2012 12:03 PM, ac [via jogamp] wrote:
> Hey guys,
>
> Since a few months ago, I have been using in Processing a set of JOGL jars
> that I build myself right before RC6. With all the RCs starting from RC6
> onwards, OpenGL Processing sketches on Mac OSX (10.6+) would just give an null
> pointer exception right after displaying the first frame or even before the
> output window is visible on the screen. The full error stack is the following:
>
> java.lang.NullPointerException
> at processing.mode.java.runner.Runner.findException(Runner.java:652)
> at processing.mode.java.runner.Runner.reportException(Runner.java:597)
> at processing.mode.java.runner.Runner.exception(Runner.java:537)
> at
> processing.mode.java.runner.EventThread.exceptionEvent(EventThread.java:367)
> at
> processing.mode.java.runner.EventThread.handleEvent(EventThread.java:255)
> at processing.mode.java.runner.EventThread.run(EventThread.java:89)
> Exception in thread "Animation Thread" java.lang.NullPointerException
> at javax.media.opengl.awt.GLCanvas.validateGLDrawable(GLCanvas.java:555)
> at javax.media.opengl.awt.GLCanvas.display(GLCanvas.java:398)
> at processing.opengl.PGL.requestDraw(Unknown Source)
> at processing.opengl.PGraphicsOpenGL.requestDraw(Unknown Source)
> at processing.core.PApplet.run(PApplet.java:1860)
> at java.lang.Thread.run(Thread.java:680)
>
> Processing can use either AWT or NEWT, but the problem happens with both.This can only happen w/ AWT's GLCanvas.
at javax.media.opengl.awt.GLCanvas.validateGLDrawable(GLCanvas.java:555)
> I was holding on to update JOGL to more a more recent RC hoping that this issue
> would go away in the meantime, but it didn't.
It would be better, if you shoot me a message ASAP when things are broken!
Well, can you point your fingers to the earliest commit/[pre-]release which
broke things ?
> I also run tests with jar files
> I built from the latest revision from the git repo, and the result is still
> the same.
>
> It seems to me that something fundamental in the way the GL drawable is
> handled on OSX changed with RC6, and this has broke OpenGL rendering in
> Processing ever since.
>
> I'm pretty much stuck with this one at this point, any hints on what to look
> for will be appreciated.Pls give me detailed instruction how I can reproduce this.
I will look into it and hope we can fix it.
It is one goal to have processing running very well
w/ current JOGL on desktop and mobile (Xerxes).
+++
I finalize the FBO stuff now, see bug 599.
Your MSAA hack should not be required anymore after 599 is solved.
+++
~Sven
URL: https://forum.jogamp.org/stuck-in-Processing-with-with-any-JOGL-release-RC6-Mac-tp4025519p4025521.html
On 07/13/2012 12:03 PM, ac [via jogamp] wrote:
> Hey guys,
>
> Since a few months ago, I have been using in Processing a set of JOGL jars
> that I build myself right before RC6. With all the RCs starting from RC6
> onwards, OpenGL Processing sketches on Mac OSX (10.6+) would just give an null
> pointer exception right after displaying the first frame or even before the
> output window is visible on the screen. The full error stack is the following:
>
> java.lang.NullPointerException
> at processing.mode.java.runner.Runner.findException(Runner.java:652)
> at processing.mode.java.runner.Runner.reportException(Runner.java:597)
> at processing.mode.java.runner.Runner.exception(Runner.java:537)
> at
> processing.mode.java.runner.EventThread.exceptionEvent(EventThread.java:367)
> at
> processing.mode.java.runner.EventThread.handleEvent(EventThread.java:255)
> at processing.mode.java.runner.EventThread.run(EventThread.java:89)
> Exception in thread "Animation Thread" java.lang.NullPointerException
> at javax.media.opengl.awt.GLCanvas.validateGLDrawable(GLCanvas.java:555)
> at javax.media.opengl.awt.GLCanvas.display(GLCanvas.java:398)
> at processing.opengl.PGL.requestDraw(Unknown Source)
> at processing.opengl.PGraphicsOpenGL.requestDraw(Unknown Source)
> at processing.core.PApplet.run(PApplet.java:1860)
> at java.lang.Thread.run(Thread.java:680)
>
> Processing can use either AWT or NEWT, but the problem happens with both.
at javax.media.opengl.awt.GLCanvas.validateGLDrawable(GLCanvas.java:555)
> I was holding on to update JOGL to more a more recent RC hoping that this issue
> would go away in the meantime, but it didn't.
It would be better, if you shoot me a message ASAP when things are broken!
Well, can you point your fingers to the earliest commit/[pre-]release which
broke things ?
> I also run tests with jar files
> I built from the latest revision from the git repo, and the result is still
> the same.
>
> It seems to me that something fundamental in the way the GL drawable is
> handled on OSX changed with RC6, and this has broke OpenGL rendering in
> Processing ever since.
>
> I'm pretty much stuck with this one at this point, any hints on what to look
> for will be appreciated.
I will look into it and hope we can fix it.
It is one goal to have processing running very well
w/ current JOGL on desktop and mobile (Xerxes).
+++
I finalize the FBO stuff now, see bug 599.
Your MSAA hack should not be required anymore after 599 is solved.
+++
~Sven
signature.asc (910 bytes) | Free forum by Nabble | Edit this page |