Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
=================================================================
==29237==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 64 byte(s) in 1 object(s) allocated from:
#0 0x7f8054948ae8 in __interceptor_malloc (/lib64/libasan.so.5+0xefae8)
#1 0x7f8051a96516 in PR_NewCondVar (/lib64/libnspr4.so+0x25516)
Direct leak of 56 byte(s) in 1 object(s) allocated from:
#0 0x7f8054948ae8 in __interceptor_malloc (/lib64/libasan.so.5+0xefae8)
#1 0x7f80541b0297 in slapi_ch_malloc (/usr/lib64/dirsrv/libslapd.so.0+0xdc297)
#2 0x7f80542ec246 in slapi_new_rwlock (/usr/lib64/dirsrv/libslapd.so.0+0x218246)
#3 0x7f80437439f1 in cl5Init ldap/servers/plugins/replication/cl5_api.c:312
#4 0x7f804375f815 in changelog5_init ldap/servers/plugins/replication/cl5_init.c:30
#5 0x7f804379f543 in multimaster_start ldap/servers/plugins/replication/repl5_init.c:801
#6 0x7f8054290213 (/usr/lib64/dirsrv/libslapd.so.0+0x1bc213)
#7 0x7f8054290ef5 in plugin_startall (/usr/lib64/dirsrv/libslapd.so.0+0x1bcef5)
#8 0x55be24df488a (/usr/sbin/ns-slapd+0x2e88a)
#9 0x7f8050b92872 in __libc_start_main (/lib64/libc.so.6+0x23872)
Direct leak of 8 byte(s) in 1 object(s) allocated from:
#0 0x7f8054948cf0 in calloc (/lib64/libasan.so.5+0xefcf0)
#1 0x7f80541b0685 in slapi_ch_calloc (/usr/lib64/dirsrv/libslapd.so.0+0xdc685)
#2 0x7f804428c61a in perfctrs_init ldap/servers/slapd/back-ldbm/perfctrs.c:42
#3 0x7f80441a25a0 in dblayer_start ldap/servers/slapd/back-ldbm/dblayer.c:1579
#4 0x7f8044294131 in ldbm_back_start ldap/servers/slapd/back-ldbm/start.c:372
#5 0x7f8054290213 (/usr/lib64/dirsrv/libslapd.so.0+0x1bc213)
#6 0x7f8054290ef5 in plugin_startall (/usr/lib64/dirsrv/libslapd.so.0+0x1bcef5)
#7 0x55be24df488a (/usr/sbin/ns-slapd+0x2e88a)
#8 0x7f8050b92872 in __libc_start_main (/lib64/libc.so.6+0x23872)
Indirect leak of 280 byte(s) in 1 object(s) allocated from:
#0 0x7f8054948cf0 in calloc (/lib64/libasan.so.5+0xefcf0)
#1 0x7f80541b0685 in slapi_ch_calloc (/usr/lib64/dirsrv/libslapd.so.0+0xdc685)
#2 0x7f804428c62c in perfctrs_init ldap/servers/slapd/back-ldbm/perfctrs.c:43
#3 0x7f80441a25a0 in dblayer_start ldap/servers/slapd/back-ldbm/dblayer.c:1579
#4 0x7f8044294131 in ldbm_back_start ldap/servers/slapd/back-ldbm/start.c:372
#5 0x7f8054290213 (/usr/lib64/dirsrv/libslapd.so.0+0x1bc213)
#6 0x7f8054290ef5 in plugin_startall (/usr/lib64/dirsrv/libslapd.so.0+0x1bcef5)
#7 0x55be24df488a (/usr/sbin/ns-slapd+0x2e88a)
#8 0x7f8050b92872 in __libc_start_main (/lib64/libc.so.6+0x23872)
Indirect leak of 168 byte(s) in 1 object(s) allocated from:
#0 0x7f8054948cf0 in calloc (/lib64/libasan.so.5+0xefcf0)
#1 0x7f8051a96470 in PR_NewLock (/lib64/libnspr4.so+0x25470)
#2 0x7f804375f815 in changelog5_init ldap/servers/plugins/replication/cl5_init.c:30
#3 0x7f804379f543 in multimaster_start ldap/servers/plugins/replication/repl5_init.c:801
#4 0x7f8054290213 (/usr/lib64/dirsrv/libslapd.so.0+0x1bc213)
#5 0x7f8054290ef5 in plugin_startall (/usr/lib64/dirsrv/libslapd.so.0+0x1bcef5)
#6 0x55be24df488a (/usr/sbin/ns-slapd+0x2e88a)
#7 0x7f8050b92872 in __libc_start_main (/lib64/libc.so.6+0x23872)
SUMMARY: AddressSanitizer: 576 byte(s) leaked in 5 allocation(s).
Version-Release number of selected component (if applicable):
389-ds-base-1.4.1.3-7.module+el8.1.0+4150+5b8c2c1f.x86_64
How reproducible:
always
Steps to Reproduce:
1. Rebuild 389-ds-base with ASAN
2. Run
tests/suites/basic/basic_test.py::test_basic_backup
tests/suites/replication/encryption_cl5_test.py::test_algorithm_unhashed[AES]
tests/suites/replication/changelog_test.py::test_verify_changelog_offline_backup
Actual results:
Memory leaks errors are reported by ASAN
Expected results:
No memory leaks
Additional info:
The leaks from the next tests will be addressed in https://pagure.io/389-ds-base/issue/49562
tests/suites/replication/encryption_cl5_test.py::test_algorithm_unhashed[AES]
tests/suites/replication/changelog_test.py::test_verify_changelog_offline_backup
I will post the BZ number later here.
Build tested: 389-ds-base-1.4.3.8-2.1asan.el8.x86_64
The following tests pass and don't produce memory leaks:
dirsrvtests/tests/suites/replication/changelog_test.py::test_verify_changelog_offline_backup
dirsrvtests/tests/suites/basic/basic_test.py::test_basic_backup
Test dirsrvtests/tests/suites/replication/encryption_cl5_test.py::test_algorithm_unhashed[AES] still produces errors, but as mentioned in comment #4, this will be addressed in a separate bz.
Marking as VERIFIED.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (389-ds:1.4 bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2020:4695
Description of problem: ================================================================= ==29237==ERROR: LeakSanitizer: detected memory leaks Direct leak of 64 byte(s) in 1 object(s) allocated from: #0 0x7f8054948ae8 in __interceptor_malloc (/lib64/libasan.so.5+0xefae8) #1 0x7f8051a96516 in PR_NewCondVar (/lib64/libnspr4.so+0x25516) Direct leak of 56 byte(s) in 1 object(s) allocated from: #0 0x7f8054948ae8 in __interceptor_malloc (/lib64/libasan.so.5+0xefae8) #1 0x7f80541b0297 in slapi_ch_malloc (/usr/lib64/dirsrv/libslapd.so.0+0xdc297) #2 0x7f80542ec246 in slapi_new_rwlock (/usr/lib64/dirsrv/libslapd.so.0+0x218246) #3 0x7f80437439f1 in cl5Init ldap/servers/plugins/replication/cl5_api.c:312 #4 0x7f804375f815 in changelog5_init ldap/servers/plugins/replication/cl5_init.c:30 #5 0x7f804379f543 in multimaster_start ldap/servers/plugins/replication/repl5_init.c:801 #6 0x7f8054290213 (/usr/lib64/dirsrv/libslapd.so.0+0x1bc213) #7 0x7f8054290ef5 in plugin_startall (/usr/lib64/dirsrv/libslapd.so.0+0x1bcef5) #8 0x55be24df488a (/usr/sbin/ns-slapd+0x2e88a) #9 0x7f8050b92872 in __libc_start_main (/lib64/libc.so.6+0x23872) Direct leak of 8 byte(s) in 1 object(s) allocated from: #0 0x7f8054948cf0 in calloc (/lib64/libasan.so.5+0xefcf0) #1 0x7f80541b0685 in slapi_ch_calloc (/usr/lib64/dirsrv/libslapd.so.0+0xdc685) #2 0x7f804428c61a in perfctrs_init ldap/servers/slapd/back-ldbm/perfctrs.c:42 #3 0x7f80441a25a0 in dblayer_start ldap/servers/slapd/back-ldbm/dblayer.c:1579 #4 0x7f8044294131 in ldbm_back_start ldap/servers/slapd/back-ldbm/start.c:372 #5 0x7f8054290213 (/usr/lib64/dirsrv/libslapd.so.0+0x1bc213) #6 0x7f8054290ef5 in plugin_startall (/usr/lib64/dirsrv/libslapd.so.0+0x1bcef5) #7 0x55be24df488a (/usr/sbin/ns-slapd+0x2e88a) #8 0x7f8050b92872 in __libc_start_main (/lib64/libc.so.6+0x23872) Indirect leak of 280 byte(s) in 1 object(s) allocated from: #0 0x7f8054948cf0 in calloc (/lib64/libasan.so.5+0xefcf0) #1 0x7f80541b0685 in slapi_ch_calloc (/usr/lib64/dirsrv/libslapd.so.0+0xdc685) #2 0x7f804428c62c in perfctrs_init ldap/servers/slapd/back-ldbm/perfctrs.c:43 #3 0x7f80441a25a0 in dblayer_start ldap/servers/slapd/back-ldbm/dblayer.c:1579 #4 0x7f8044294131 in ldbm_back_start ldap/servers/slapd/back-ldbm/start.c:372 #5 0x7f8054290213 (/usr/lib64/dirsrv/libslapd.so.0+0x1bc213) #6 0x7f8054290ef5 in plugin_startall (/usr/lib64/dirsrv/libslapd.so.0+0x1bcef5) #7 0x55be24df488a (/usr/sbin/ns-slapd+0x2e88a) #8 0x7f8050b92872 in __libc_start_main (/lib64/libc.so.6+0x23872) Indirect leak of 168 byte(s) in 1 object(s) allocated from: #0 0x7f8054948cf0 in calloc (/lib64/libasan.so.5+0xefcf0) #1 0x7f8051a96470 in PR_NewLock (/lib64/libnspr4.so+0x25470) #2 0x7f804375f815 in changelog5_init ldap/servers/plugins/replication/cl5_init.c:30 #3 0x7f804379f543 in multimaster_start ldap/servers/plugins/replication/repl5_init.c:801 #4 0x7f8054290213 (/usr/lib64/dirsrv/libslapd.so.0+0x1bc213) #5 0x7f8054290ef5 in plugin_startall (/usr/lib64/dirsrv/libslapd.so.0+0x1bcef5) #6 0x55be24df488a (/usr/sbin/ns-slapd+0x2e88a) #7 0x7f8050b92872 in __libc_start_main (/lib64/libc.so.6+0x23872) SUMMARY: AddressSanitizer: 576 byte(s) leaked in 5 allocation(s). Version-Release number of selected component (if applicable): 389-ds-base-1.4.1.3-7.module+el8.1.0+4150+5b8c2c1f.x86_64 How reproducible: always Steps to Reproduce: 1. Rebuild 389-ds-base with ASAN 2. Run tests/suites/basic/basic_test.py::test_basic_backup tests/suites/replication/encryption_cl5_test.py::test_algorithm_unhashed[AES] tests/suites/replication/changelog_test.py::test_verify_changelog_offline_backup Actual results: Memory leaks errors are reported by ASAN Expected results: No memory leaks Additional info: