(ITS#9168) Memory Leak in LDAP search operation

[bananashake2004@yahoo.de]

Full_Name: Stefan Koch
Version: 2.4.44
OS: Debian Stretch
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (2001:4dd0:f0a3:2:a44f:a486:843b:bdde)


Valgrind shows a memory leak in slapd that will lead to successive increment of
memory consumption at runtime.

valgrind --tool=memcheck --leak-check=yes --num-callers=50 /usr/sbin/slapd -d

[...]

==26332== 22,000 (80 direct, 21,920 indirect) bytes in 1 blocks are definitely
lost in loss record 1,768 of 1,791
==26332== at 0x4C2DBC5: calloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==26332== by 0x5090D24: ber_memcalloc_x (in
/usr/lib/x86_64-linux-gnu/liblber-2.4.so.2.10.7)
==26332== by 0x15CEC2: ch_calloc (in /usr/sbin/slapd)
==26332== by 0x9D8582C: ???
==26332== by 0x9D8E048: ???
==26332== by 0x143E40: fe_op_search (in /usr/sbin/slapd)
==26332== by 0x143803: do_search (in /usr/sbin/slapd)
==26332== by 0x141485: ??? (in /usr/sbin/slapd)
==26332== by 0x141764: ??? (in /usr/sbin/slapd)
==26332== by 0x4E47FD9: ??? (in
/usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2.10.7)
==26332== by 0x69024A3: start_thread (pthread_create.c:456)

==26332== LEAK SUMMARY:
==26332== definitely lost: 3,555 bytes in 209 blocks
==26332== indirectly lost: 22,510 bytes in 297 blocks
==26332== possibly lost: 41,688 bytes in 66 blocks
==26332== still reachable: 4,749,541 bytes in 10,436 blocks
==26332== suppressed: 0 bytes in 0 blocks

This bug was already reported here:
https://www.openldap.org/lists/openldap-devel/200507/msg00053.html