Found a few leaks after running the cleanallruv_test.py CI test with an ASAN build
https://pagure.io/389-ds-base/pull-request/50309
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None
commit 6c2bb66 --> master
f7d7179..85c3c30 389-ds-base-1.4.0 -> 389-ds-base-1.4.0
Metadata Update from @mreynolds: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
There was a compiler warning, and it turns out the replication part of the fix did not address the issue. There is still this leak:
Direct leak of 5952 byte(s) in 372 object(s) allocated from: #0 0x7f0117e8ce50 in calloc (/lib64/libasan.so.5+0xeee50) #1 0x7f01176fe8c5 in slapi_ch_calloc ldap/servers/slapd/ch_malloc.c:175 #2 0x7f01177027ba in csn_dup ldap/servers/slapd/csn.c:118 #3 0x7f0105c8932c in get_csn_internal ldap/servers/plugins/replication/repl5_ruv.c:522 #4 0x7f0105c8932c in get_csn_internal ldap/servers/plugins/replication/repl5_ruv.c:502 #5 0x7f0105c08b82 in clcache_refresh_local_maxcsn ldap/servers/plugins/replication/cl5_clcache.c:592 #6 0x7f0105c8c5e6 in ruv_enumerate_elements ldap/servers/plugins/replication/repl5_ruv.c:994 #7 0x7f0105c0b27e in clcache_refresh_local_maxcsns ldap/servers/plugins/replication/cl5_clcache.c:617 #8 0x7f0105c0b27e in clcache_load_buffer ldap/servers/plugins/replication/cl5_clcache.c:337 #9 0x7f0105bf19a8 in _cl5PositionCursorForReplay ldap/servers/plugins/replication/cl5_api.c:5259 #10 0x7f0105bf6e94 in cl5CreateReplayIterator ldap/servers/plugins/replication/cl5_api.c:1483 #11 0x7f0105c49a49 in send_updates ldap/servers/plugins/replication/repl5_inc_protocol.c:1560 #12 0x7f0105c49a49 in repl5_inc_run ldap/servers/plugins/replication/repl5_inc_protocol.c:1055 #13 0x7f0105c5929f in prot_thread_main ldap/servers/plugins/replication/repl5_protocol.c:255 #14 0x7f0114ffa3f7 (/lib64/libnspr4.so+0x2a3f7)
Reopening...
Metadata Update from @mreynolds: - Issue status updated to: Open (was: Closed)
Remove changelog "fix" from last commit since it didn't actually do anything
6c2bb66..1808f31 master -> master
85c3c30..11430af 389-ds-base-1.4.0 -> 389-ds-base-1.4.0
is it still open ?
Not any more!
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/3367
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.