Just starting the server up, and then stopping it generates these leaks. Putting the server under load still leads to the same leaks:
==17652== 48 bytes in 3 blocks are definitely lost in loss record 570 of 1,327 ==17652== at 0x4C2745D: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) ==17652== by 0x518FC5A: ns_thrpool_new (ns_thrpool.c:811) ==17652== by 0x41D34A: slapd_daemon (daemon.c:1516) ==17652== by 0x42679A: main (main.c:1279) ==17652== ==17652== 264 (128 direct, 136 indirect) bytes in 1 blocks are definitely lost in loss record 1,031 of 1,327 ==17652== at 0x4C291D4: calloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) ==17652== by 0x518F02D: new_ns_job (ns_thrpool.c:367) ==17652== by 0x518F0EF: alloc_io_context (ns_thrpool.c:384) ==17652== by 0x518F7DA: setup_event_q_wakeup (ns_thrpool.c:663) ==17652== by 0x518FC47: ns_thrpool_new (ns_thrpool.c:808) ==17652== by 0x41D34A: slapd_daemon (daemon.c:1516) ==17652== by 0x42679A: main (main.c:1279) ==17652== ==17652== 528 (128 direct, 400 indirect) bytes in 1 blocks are definitely lost in loss record 1,104 of 1,327 ==17652== at 0x4C291D4: calloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) ==17652== by 0x518F02D: new_ns_job (ns_thrpool.c:367) ==17652== by 0x518F1A1: alloc_signal_context (ns_thrpool.c:403) ==17652== by 0x518F46D: ns_add_signal_job (ns_thrpool.c:537) ==17652== by 0x41D37B: slapd_daemon (daemon.c:1517) ==17652== by 0x42679A: main (main.c:1279)
DS Patch 0001-Ticket-48110-Free-all-the-nunc-stans-signal-jobs-whe.patch
nunc-stans patch 0001-Ticket-48110-Fix-nunc-stans-memory-leaks.patch
To git+ssh://git.engineering.redhat.com/srv/git/users/mareynol/nunc-stans.git f4b7f8c..f232119 mreynolds -> mreynolds commit f2321199cfe087e20a9045408c0a3fd9c027589e
To git+ssh://git.engineering.redhat.com/srv/git/users/mareynol/ds.git ecadfd7..e3c1f1f nunc-stans -> nunc-stans commit e3c1f1f793689584209fb77e7e1bce15a6371987
nunc-stans part moved to https://fedorahosted.org/nunc-stans/ticket/16
Metadata Update from @mreynolds: - Issue assigned to mreynolds - Issue set to the milestone: 1.3.4 backlog
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1441
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.