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

Re: OpenLDAP 2.0.7 problems with binds (ITS#988)



I compiled my version under Solaris 8, with gcc 2.xxx, which I've been told
*might* have a problem regarding memory leaks.

Does anyone know if this is true?

I'm interested to see if anyone has compiled 2.0.7 using cc instead, and
whether it has the same issue.

"Dr. Ian C. Smith" wrote:

> I'd be very interested to hear if anyone else has had similar problems and
> even more interested to hear of any solutions. I performed a similar
> experiment and the server seemed to be leaking huge amounts of memory -
> around 2 MB per 1000 binds (anonymous or simply authenticated) wasn't being
> freed. It seemed to keep rising linearly up to 50k binds -- 115 MB of RAM
> gone !
>
> regards,
>
> -ian.
>
> ----------------------------------------------
> Ian C. Smith,
> e-mail: i.c.smith@liverpool.ac.uk
> Address: Computer Sevices Department,
>          Brownlow Hill Building - room G11,
>          The University of Liverpool,
>          Liverpool L69 3BX.
> --On Wednesday, January 24, 2001 8:03 PM +0000 donnelly@ldapman.org wrote:
>
> > Full_Name: Michael Donnelly
> > Version: 2.0.7
> > OS: Solaris 8
> > URL: ftp://ftp.openldap.org/incoming/
> > Submission from: (NULL) (63.211.143.38)
> >
> >
> > I've noticed that using OpenLDAP 2.0.7, the closing of an LDAP connection
> > does not
> > seem to free all the resources used during that connection.
> >
> > For example, bind (as a user) and immedaitely close the connection.
> > (password verification is one reason you might do this.)  Now repeat this
> > 50,000 times.
> >
> > You'll see the amount of RAM used steadily increase, until eventually
> > slapd will
> >
> > core dump.   On my system, a Sun E250 with 2 CPUs and 1GB of ram, I get
> > about 700K
> > connections before the server drops dead.