[Issue 9365] Mem leaks with Æ-DIR providers

https://bugs.openldap.org/show_bug.cgi?id=9365 --- Comment #6 from Michael Ströder <michael(a)stroeder.com&gt; --- I've retested with latest RE24 with the commit and the output still contains this: ==898== 47,104 bytes in 23 blocks are indirectly lost in loss record 95 of 96 ==898== at 0x483BB65: calloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) ==898== by 0x49FA5F5: build_trtable (/usr/src/debug/glibc-2.32-1.1.x86_64/posix/regexec.c:3403) ==898== by 0x49FCC04: transit_state (/usr/src/debug/glibc-2.32-1.1.x86_64/posix/regexec.c:2252) ==898== by 0x49FCC04: check_matching (/usr/src/debug/glibc-2.32-1.1.x86_64/posix/regexec.c:1120) ==898== by 0x49FCC04: re_search_internal (/usr/src/debug/glibc-2.32-1.1.x86_64/posix/regexec.c:792) ==898== by 0x4A0126B: regexec@@GLIBC_2.3.4 (/usr/src/debug/glibc-2.32-1.1.x86_64/posix/regexec.c:218) ==898== by 0x54DEA84: sock_over_op (/usr/src/debug/openldap2-2.4.54-14.1.x86_64/servers/slapd/back-sock/config.c:301) ==898== by 0x1BAA39: overlay_op_walk (/usr/src/debug/openldap2-2.4.54-14.1.x86_64/servers/slapd/backover.c:661) ==898== by 0x1BABAA: over_op_func (/usr/src/debug/openldap2-2.4.54-14.1.x86_64/servers/slapd/backover.c:730) ==898== by 0x168230: fe_op_bind (/usr/src/debug/openldap2-2.4.54-14.1.x86_64/servers/slapd/bind.c:383) ==898== by 0x167840: do_bind (/usr/src/debug/openldap2-2.4.54-14.1.x86_64/servers/slapd/bind.c:205) ==898== by 0x1482C1: connection_operation.lto_priv.0 (/usr/src/debug/openldap2-2.4.54-14.1.x86_64/servers/slapd/connection.c:1175) ==898== by 0x148E3A: connection_read_thread (/usr/src/debug/openldap2-2.4.54-14.1.x86_64/servers/slapd/connection.c:1311) ==898== by 0x4860C41: ldap_int_thread_pool_wrapper.part.0 (/usr/src/debug/openldap2-2.4.54-14.1.x86_64/libraries/libldap_r/tpool.c:696) For the tests I've disabled background jobs and all other replicas and I've sent simple bind operation 59 times. So to me the count of 23 does not seem to correlate with the number of operations. -- You are receiving this mail because: You are on the CC list for the issue.