Re: memory leak

"Walter C. Pelissero" <[email protected]> writes:

> The following ugly patches, based on just a very superficial
> understanding of CLG innards, seem to fix the memory leak in the list
> and tree stores.  I'm not sure, though, the leak hasn't deeper roots.
> As far as I know it could be that any object ending in a container may
> suffer of this reference count problem; I haven't checked it.

Thanks for tracking down this memory leak. I've fixed it by adding an
optional temp-p argument to gvalue-init which is used in the call from
the with-gvalue macro.

I've also applied your other patches.

-- 
Espen

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/