Bug 62 - errors from glGetError(), not clearing
Summary: errors from glGetError(), not clearing
Alias: None
Product: Jogl
Classification: JogAmp
Component: core (show other bugs)
Version: 1
Hardware: All windows
: P3 normal
Assignee: Sven Gothel
Depends on:
Reported: 2004-02-05 01:30 CET by Sven Gothel
Modified: 2010-03-24 07:46 CET (History)
0 users

See Also:
SCM Refs:
Workaround: ---

Zip file of Java project (3.25 KB, application/x-compressed)
2004-02-05 13:31 CET, Sven Gothel

Note You need to log in before you can comment on or make changes to this bug.
Description Sven Gothel 2010-03-24 07:46:14 CET

---- Reported by andyskinner 2004-02-05 13:30:12 ----

We've got a fairly complex project that has been using the old Jogl project from 
years ago.  We've maintained our own version, but now we'd like to see if this Jogl 
project can help us with more platforms.

Our project uses a separate thread for rendering, and I've built a callback system 
where the first display() from AWT tells the rendering to get going, and then that 
rendering thread asks for a display, specifying the method to be called.

I recently found and tried the nightly builds.  Maybe it isn't fair to report issues 
against those, but there has been a release since September, so I decided to try 
those.  I'm running into problems that aren't there in the September version.

When I use the DebugGL, I get an out of memory error.  It seems that glGetError() 
is checked frequently, and when it is, is called repeatedly until it clears.  But it 
never seems to clear, and the string with the messages in it grows until it can't 

When I try the TraceGL, I don't get this problem, but I can see that the places 
I've called glGetError() a single time to report an invalid operation, and that the 
error is set sometime in between my display() calls.  I don't think it is reporting 
something I've done.

I've got a zipped project of java files that I will append to this report if I can.

JoglObj is my interface to Jogl, and it implements GLEventListener and the callback 
system I mention.  JoglPanel is the GLCanvas' parent, and it contains the rendering 
thread object.

If you remove the lines in JoglObj.renderJogl() about setting the no auto redraw 
mode and the render thread, you don't get any problems.  But I'm having thread 
issues as well (in the September version), and I need to be able to address them.


---- Additional Comments From andyskinner 2004-02-05 13:31:44 ----

Created an attachment
Zip file of Java project

---- Additional Comments From kbr 2005-01-31 00:04:20 ----

Sorry for not commenting on this bug until now. Many bugs and workarounds for
OpenGL driver bugs relating to multithreading have recently been fixed in JOGL.
Please test with 1.1 b07 and, if problems persist, with the forthcoming 1.1 b08
and reopen this bug if you still see problems. The test application works fine
on my system (Windows XP, NVidia Quadro FX Go700).

--- Bug imported by sgothel@jausoft.com 2010-03-24 07:46 EDT  ---

This bug was previously known as _bug_ 62 at https://jogl.dev.java.net/bugs/show_bug.cgi?id=62
Imported an attachment (id=17)

The original submitter of attachment 17 [details] is unknown.
   Reassigning to the person who moved it here: sgothel@jausoft.com.