Hi Stephan,

Thanks for reporting this bug, indeed the
osg::BufferObject::flushDeletedBufferObjects(..) was never called from
SceneView like is should have been, I have just added this to my
version of the OSG and will check it in later once everything is
built.

I have had to modify both the include/osg/BufferObject header changing
flushDeletedBufferObjects to static, and adding a call to it in
SceneView::flushDeletedGLObjects.

Long term I'd like to have an automatic system for registering OpenGL
objects handlers that need cleaning up.  This will have to wait till I
have more time available and stronger wrists...

Robert.

On 4/3/07, Stephan Huber <[EMAIL PROTECTED]> wrote:
Hi

I am experiencing Memoryleaks with PixelBufferObjects. I am playing
quicktime-videos which I load on the fly and dispose them after playing
them. The quicktimes  use  PixelBufferObjects to get better performance
on Windows.

It seems that the created PixelBufferObjects get never released, so the
computer's memory get filled with unused PixelBufferObjects.

After a quick look on the osg-source I could not find any file which
calls osg::BufferObject::flushDeletedBufferObjects(), it seems that this
call should be placed in SceneView::flushDeletedGLObjects.

Is my assumption correct? Are there any other places where the
BufferObject-Method should be called?

I am working with osg-1.2 and can't update to HEAD in the near future. (
I did check HEAD) However I will try to fix the bug, when my assumptions
are correct and submit the fix to osg-submission


Thanks in advance,
Stephan


_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/

_______________________________________________
osg-users mailing list
[email protected]
http://openscenegraph.net/mailman/listinfo/osg-users
http://www.openscenegraph.org/

Reply via email to