plib-devel

[Plib-devel] RE: Deinitializing PUI

[Fay J. F C. AAC/W. <joh...@eg...>]

Some more on the PUI memory leaks ...

The "puInit" function creates a "puInterface" object.  When I created a
"puDeinit" function which deleted the object, the number of leaked memory
blocks dropped from eleven to eight.  Of these remaining eight, five contain
the strings "NULL", "puValue", "puObject", "puGroup", and "puInterface".  I
suspect the RTTI library here.

While it's not a serious matter--the leakage is on a per-widget-type basis,
not a per-widget basis--it's still bad form to leak memory.  Is there
somebody who can look at the "ulRTTI" library and see what can be done about
it?

John F. Fay
joh...@eg...

Re: [Plib-devel] RE: Deinitializing PUI

[Steve B. <sjb...@ai...>]

Fay John F Contr AAC/WMG wrote:
> Some more on the PUI memory leaks ...
> 
> The "puInit" function creates a "puInterface" object.  When I created a 
> "puDeinit" function which deleted the object, the number of leaked 
> memory blocks dropped from eleven to eight.  Of these remaining eight, 
> five contain the strings "NULL", "puValue", "puObject", "puGroup", and 
> "puInterface".  I suspect the RTTI library here.
> 
> While it's not a serious matter--the leakage is on a per-widget-type 
> basis, not a per-widget basis--it's still bad form to leak memory.  Is 
> there somebody who can look at the "ulRTTI" library and see what can be 
> done about it?

Since we plan to use RTTI for SSG also - it's an important matter. SSG
nodes get allocated and deallocated in significant quantities all the
time in some applications.

---------------------------- Steve Baker -------------------------
HomeEmail: <sjb...@ai...>    WorkEmail: <sj...@li...>
HomePage : http://web2.airmail.net/sjbaker1
Projects : http://plib.sf.net    http://tuxaqfh.sf.net
            http://tuxkart.sf.net http://prettypoly.sf.net