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

Re: slapd memory leak (ITS#249)

Dirk Nehring wrote:
> On Wed, Aug 18, 1999 at 08:10:55AM -0700, Kurt D. Zeilenga wrote:
> > At 11:55 AM 8/18/99 GMT, dnehring@telemedia.de wrote:
> > >Unfortunatly, it doesn't help. slapd is eating memory for lunch when
> > >modifying many entries. I have no idea.
> >
> > Without decent tools, one has to resort to a process of elimination.
> > I suggest now trying --without-threads --with-ldbm-api=gdbm.
> Hmmh, that seems to be very much work to test different backends. Is
> there no change to reproduce the problem (10000 entries in a database
> and write an LDIF file for updating 1 attribute of each entry)? If not,
> I'll try to set up a test enviroment to track the memory leak further
> down.

Dirk, I hacked up the devel test008-concurrency test such that I
could plug in different slapd (including non-threaded/gdbm).  The
test uses add/delete, not modify, but I do see memory growth
similiar to what you describe.  We are digging, but the more
eyes the better...