John Morrissey wrote:
Any response to this, Howard? slapd finally consumed enough memory on this
machine that the kernel OOM killer terminated it, but this problem is
trivial for us to reproduce (happens after a few days of slapd uptime).
If it's so easily reproducible you should be able to recreate this while
running a heap profiler. Can you get hold of google's tcmalloc and run with
that? If it's not already on your platform, you can get it here
http://code.google.com/p/google-perftools/
You don't need to recompile slapd to use it. Just set
LD_PRELOAD=/path/to/tcmalloc before running slapd. (But you still need
debugging/symbols.) See the docs here
http://google-perftools.googlecode.com/svn/trunk/doc/heapprofile.html
you should also set HEAPPROFILE to the path where to dump the profile log.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
