Hello Vincenzo,
Vincenzo Marafioti wrote:
> I had experienced some memory leak due to FBOViewport render and
> setDirty(bool).
> Here some OpenSG 1.8 code lines taken from OSGFBOViewport.cpp
>
> ...
> bool FBOViewport::initialize(Window *win, Int32 format){
> ...
> if (getFrameBufferIndex() && !getDirty())
> return true;
> //generating new fbo, render buffer.. ect.
>
> ..
> }
> ...
>
> I realize that when I need to setDrity(true) (for example to resize
> FBO), OpenSG will generate a new FBO without clears the previous one. It
> is correct? There are some methods in order to clear it and avoid memory
> leak?
yes, it looks like that is indeed the case and I'd say it is a bug.
initialize() should handle the case when getFrameBufferIndex() != 0 by
either reusing the existing FBO or at least free it and allocate a new one.
I'm fairly swamped at the moment, so it will be a couple of days at
least before I can look into it, perhaps you'd like to take a stab at
this and send a patch?
Cheers,
Carsten
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users
