Posted by Sven Gothel on Jan 11, 2014; 2:28am
URL: https://forum.jogamp.org/JOGL-Printing-Error-on-Boot-tp4031154p4031155.html

On 01/11/2014 03:24 AM, bgroenks96 [via jogamp] wrote:
> I just updated my lazily not up-to-date JOGL JARs and natives to the most
> recent stable build from jogamp-all-platforms.7z
>
> I now get this message every time the GLContext initializes:
> Info: GLDrawableHelper.reshape: pre-exisiting GL error 0x501
>
> It doesn't appear to really affect anything, but I just want to know if I can
> fix it.

Run you application w/ debug property 'jogl.debug.DebugGL',
i.e. 'java .. -Djogl.debug.DebugGL  yourMain'

This will throw an exception ASAP when one of the GL commands
results in an error and also enabled the native debug context if available.

Use 'jogl.debug.TraceGL' for excessive GL command trace.

>
> Also, is it necessary to call destroy() on a NEWT Window, Screen, and Display
> before exit?  I seem to end up with errors on exit quite often if I do this.

Just the window itself, see the many NEWT unit tests.
NEWT uses add/remove reference on it's referenced Screen/Display
aggregations.

~Sven