[Date Prev][Date Next]
Re: (ITS#7299) Memory leaks when using ldapmodify to add members to groupOfNames objectclass
- To: openldap-its@OpenLDAP.org
- Subject: Re: (ITS#7299) Memory leaks when using ldapmodify to add members to groupOfNames objectclass
- From: email@example.com
- Date: Fri, 15 Jun 2012 13:16:57 GMT
- Auto-submitted: auto-generated (OpenLDAP-ITS)
> Full_Name: Jan Synacek
> Version: git (c73ec15)
> OS: linux-fedora17
> URL: http://jsynacek.fedorapeople.org/openldap/leak/openldap-mmr-leak.tar.gz
> Submission from: (NULL) (184.108.40.206)
> I'm using a 2-node mmr setup on my local machine - configuration files and
> 'uploader' scripts are provided in the archive.
> 1) I have the two nodes running.
> 2) Execute run.sh (only a wrapper for ldapusradm.sh) and start monitoring
> slapd's memory usage.
> 3) After some time (at about 2k users on my system), slapd consumes a large
> amount of memory which is still growing
> Note that not using ldapmodify to add members to 'cn=users,dc=yes,dc=my', but
> using it e.g. for modifying each user's email, does NOT result in any memory
> I have also created a massif output using valgrind's massif tool:
> I found a very similar bug (#7292), but I'm not sure if it's related.
Running RE24 with valgrind --leak-check=full I see no leak when running your
test. That should be the same as git c73ec15. No idea what leak you're seeing.
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/