--On Wednesday, September 29, 2010 12:38 AM +0000 quanah@zimbra.com wrote:

...

It appears to be a problem with the entry cache, which is set to 25,000:

Running with a fix from Howard, the entry cache behaves correctly. However, slapd still grows at the same rate.

If I limit to only 10 paged results searches, slapd grows at a rate of 300MB Virtual and 300MB Resident for every set of 10 paged results searches I do concurrently, up until I run slapd out of memory. There's something very wrong with paged results searches.

Could it be configuration-specific? I tested with a plain configuration resulting from test003; maybe some player in the middle, say, is causing entries to be duplicated and leaked, or read-locks on originals are not released correctly? Can you post a configuration that shows the issue?

p.