Why glGetError calls?

Hello jogl devs! Can someone explain to me why all the glGetError() calls in GLBufferObjectTracker and GLBufferStateTracker? Aren't glGetError() calls supposed to be expensive? And what's the point of checking unrecoverable error when buffers are created? Are they merely made for backward-compatibility (I saw comments about mesa, is it still alive?)

I turned it off in my own project and performance of drawing WorldWind annotations seems improving, jumped from 80+FPS to 130+FPS with several dozens of annotation labels.

On 09/12/2014 04:10 PM, aqd [via jogamp] wrote:
> Hello jogl devs! Can someone explain to me why all the glGetError() calls in
> GLBufferObjectTracker and GLBufferStateTracker? Aren't glGetError() calls
> supposed to be expensive? And what's the point of checking unrecoverable error
> when buffers are created? Are they merely made for backward-compatibility (I
> saw comments about mesa, is it still alive?)
>
> I turned it off in my own project and performance of drawing WorldWind
> annotations seems improving, jumped from 80+FPS to 130+FPS with several dozens
> of annotation labels.

Interesting point, i.e. performance vs error-checking.
The latter uses glGetError() and indeed forces the driver to synchronize.

I filed Bug 1066 <https://jogamp.org/bugzilla/show_bug.cgi?id=1066>
to cover this issue - please add yourself to the CC list
to continue the discussion there.

Thank you!

~Sven

Thanks!

On 09/13/2014 07:50 PM, aqd [via jogamp] wrote:
> Thanks!

Your cooperation is strongly requested.
Didn't you receive the comments ?

Please read:

  Bug 1066 <https://jogamp.org/bugzilla/show_bug.cgi?id=1066>

Cheers, Sven