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

Re: (ITS#5860) slapd memeory leak under openldap 2.4

rlvcosta@yahoo.com wrote:
> --0-1358063323-1230648878=:64021
> Content-Type: text/plain; charset=iso-8859-1
> Content-Transfer-Encoding: quoted-printable
> Pierangelo,
> I could run the valgrind but at this time I do not have the DB with the aro=
> und 4 million subscribers. In this condition, with a small number of users,=
>  I already could see some "definitive" memory leaks and I believe they are =
> associated with OpenLdap.
> Just for a history I already compiled the openldap 2.4.11 souce code withou=
> t modules and TLS since many lists make reference to some possible issues i=
> n RHEL with TLS. Even so I could not have a load without the possible memor=
> y leak.
> So I do not believe the problems are in the RHEL libtool or glibc.
> In any case the result for the valgrind is (short number of entrances at th=
> is time):

You probably need to use an unstripped binary in order to find out where 
mallocs/frees occur.  Most of the occurrences you notice are either 
one-time leaks.  Moreover, 2.4.13 is out, and it might have fixed some. 
  I suggest you further investigate using the latest code, using an 
unstripped binary.


Ing. Pierangelo Masarati
OpenLDAP Core Team

SysNet s.r.l.
via Dossi, 8 - 27100 Pavia - ITALIA
Office:  +39 02 23998309
Mobile:  +39 333 4963172
Fax:     +39 0382 476497
Email:   ando@sys-net.it