Hello Carsten,
removal of FBO seems to work now. Thanks.
While debugging I found out that the size of DisplayLists and VBO's increase also. Seems the initial set gets recreated with each Screenshot, and of course never destructed. I guess the PassiveWindow causes this as OpenSG links GLObjects to a specific window, correct? I think that's not the behavior I need as all the (gl)objects I need for the screenshot are already created. What I need to do is to redirect the rendering content from my main window to a specific FBO as the screenshot may have a different size as the main window. Is there a better/more efficient way to do this?
Thanks,
Michael
Gesendet: Freitag, 26. September 2014 um 07:54 Uhr
Von: "Carsten Neumann" <carsten.p.neum...@gmail.com>
An: opensg-users@lists.sourceforge.net
Betreff: Re: [Opensg-users] FBO cleanup
Von: "Carsten Neumann" <carsten.p.neum...@gmail.com>
An: opensg-users@lists.sourceforge.net
Betreff: Re: [Opensg-users] FBO cleanup
Hello Michael,
On 09/25/2014 04:00 PM, Michael Raab wrote:
> I'm using a passive window with a FBOViewport attached to create
> screenshots. Works great, but while searching for a memory leak, I found
> out that the FBO attached to the FBOViewport gets not cleaned up.
> The OpenSG FieldContainers for the FBO, FBOViewport and PassiveWindow
> get destructed but glDeleteFramebuffer or glDeleteFramebufferEXT are
> never called. This should be done by FrameBufferObject::handleDestroyGL
> but this never gets called. Actually I don't know why?! Could someone
> please have I look?
is the Window going away at the same time as the FBO? In that case there
is no Window::doFrameExit run after the FBO is destroyed, so there is no
period where the OpenGL context is active and the corresponding GL
object can be cleaned up - in general GL objects are only destroyed at
the end of the (following) frame.
To allow the Window to perform this cleanup without rendering a frame
you can call Window::runFrameExit.
Cheers,
Carsten
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Opensg-users mailing list
Opensg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensg-users
On 09/25/2014 04:00 PM, Michael Raab wrote:
> I'm using a passive window with a FBOViewport attached to create
> screenshots. Works great, but while searching for a memory leak, I found
> out that the FBO attached to the FBOViewport gets not cleaned up.
> The OpenSG FieldContainers for the FBO, FBOViewport and PassiveWindow
> get destructed but glDeleteFramebuffer or glDeleteFramebufferEXT are
> never called. This should be done by FrameBufferObject::handleDestroyGL
> but this never gets called. Actually I don't know why?! Could someone
> please have I look?
is the Window going away at the same time as the FBO? In that case there
is no Window::doFrameExit run after the FBO is destroyed, so there is no
period where the OpenGL context is active and the corresponding GL
object can be cleaned up - in general GL objects are only destroyed at
the end of the (following) frame.
To allow the Window to perform this cleanup without rendering a frame
you can call Window::runFrameExit.
Cheers,
Carsten
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Opensg-users mailing list
Opensg-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensg-users
------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________ Opensg-users mailing list Opensg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensg-users
