Hi Vaibhav,

On Thu, 2006-09-07 at 15:10 +0530, Vaibhav Saxena wrote:
> > delete mgr;
> > subRefCP(scene);
> > subRefCP(gwin);
>
> Just curious, why are these statements not already present in the
> sample examples, any particular reason ?

For large trees the cleanup can actually take a long time if you do it
piece by piece. Given that the operating system cleans up all the
applications resources on exit anyway, there was never a compelling
reason to do it.

> Anyways, I tried this and the amount of memory leaked indeed goes down
> but still present. Here is the new memory dump statistics for program
> 2 after putting above 3 statements :
> 
> With OpenSG 1.6 : 96221 bytes leaked (earlier it was 343000 bytes)
> With OpenSG CVS build :  139052 bytes leaked ( earlier it was 350116 bytes)
> 
> However the statement subRefCP(scene) causes following warning to be
> thrown by the application when exitting :
> 
> With OpenSG 1.6 :
> WARNING: FieldContainerFactory::unregisterFieldContainer:id -572662307
> inconsisent with store size 172!
> 
> With OpenSG CVS build :
> WARNING:  FieldContainerFactory::unregisterFieldContainer:id
> -572662307 inconsistent with store size 182!
> 
> Is something incorrect here ?

Yeah, the delete mgr will clean up the scene, too, so if you don't have
another reference to it, you get double frees, which are not handled
very gracefully.

As I said, I'm personally more worried about leaks in a running
application, so those 140k don't worry me very much.

Yours

        Dirk



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users

Reply via email to