[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#6330) slapd memory leak

--On Friday, October 16, 2009 7:57 AM +0000 masarati@aero.polimi.it wrote:

> hyc@symas.com wrote:
>> whm@stanford.edu wrote:
>>> Here is the valgrind output.  The complete log is at
>>>    http://www.stanford.edu/~whm/files/slapd/valgrind-memcheck.txt
>> All of this indicates memory leaks and errors in the SASL library, not
>> any bug  in OpenLDAP.
> That was exactly my suspect when you originally stated that the leak
> only appeared after wrapping dynlist requests within a SASL bind/unbind.
>   The leak could still be related to an improper use of SASL library
> calls by OpenLDAP, although unlikely.  However, that valgrind output
> does not help as leaks related to malloc are too hidden into SASL; you
> should add --num-callers=<more than 12, the default; enough to see
> something related to OpenLDAP's code>.

Given that the memory issue is not seen with OpenLDAP 2.3 + dyngroup, I'd 
still have to agree there's something wrong with what OpenLDAP 2.4 + 
dynlist is doing.



Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
Zimbra ::  the leader in open source messaging and collaboration