https://bugs.openldap.org/show_bug.cgi?id=9924
--- Comment #9 from Howard Chu hyc@openldap.org --- (In reply to Michael Ströder from comment #7)
--- Comment #6 from Howard Chu hyc@openldap.org --- Triggering the leak requires first exhausting the per-thread tmpmem allocator, so you need a fairly large search response set with a lot of returned deref values.
What does "fairly large" mean? A few thousand entries? Or a millions?
The tmpmem allocator can handle up to 1MB by default, so the size of a single search response entry plus all of the deref values must consume more than 1MB to trigger the leak.