#48131 memory leak when deleting entry
Closed: wontfix Opened by mreynolds.

==18131== 32 bytes in 1 blocks are possibly lost in loss record 475 of 1,440
==18131==    at 0x4C2745D: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==18131==    by 0x4E82A12: slapi_ch_malloc (ch_malloc.c:155)
==18131==    by 0x4F0244C: value_new (value.c:183)
==18131==    by 0x4F024C1: slapi_value_dup (value.c:172)
==18131==    by 0x4F04598: valueset_set_valueset (valueset.c:1205)
==18131==    by 0x4E7C1E6: slapi_attr_dup (attr.c:440)
==18131==    by 0x4E923C7: slapi_entry_dup (entry.c:2163)
==18131==    by 0x123FDBBE: backentry_dup (backentry.c:114)
==18131==    by 0x12442DAD: modify_apply_mods_ignore_error (ldbm_modify.c:82)
==18131==    by 0x124582A6: parent_update_on_childchange (parents.c:212)
==18131==    by 0x12437D6F: ldbm_back_delete (ldbm_delete.c:556)
==18131==    by 0x4E86B3F: op_shared_delete (delete.c:364)
==18131==    by 0x4E86DF2: do_delete (delete.c:128)
==18131==    by 0x41841E: connection_threadmain (connection.c:650)
==18131==    by 0x7168C2A: ??? (in /usr/lib64/libnspr4.so)
==18131==    by 0x77A7EE4: start_thread (in /usr/lib64/libpthread-2.18.so)
==18131==    by 0x7AB1D1C: clone (in /usr/lib64/libc-2.18.so)
==18131== 32 bytes in 1 blocks are possibly lost in loss record 476 of 1,440
==18131==    at 0x4C2745D: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==18131==    by 0x4E82A12: slapi_ch_malloc (ch_malloc.c:155)
==18131==    by 0x4F0244C: value_new (value.c:183)
==18131==    by 0x4F024C1: slapi_value_dup (value.c:172)
==18131==    by 0x4F042A4: slapi_valueset_add_attr_valuearray_ext (valueset.c:1126)
==18131==    by 0x4E7D1E3: attrlist_merge_valuearray (attrlist.c:132)
==18131==    by 0x4E9317C: slapi_entry_attr_merge_sv (entry.c:2722)
==18131==    by 0x4E931C6: slapi_entry_attr_merge (entry.c:2714)
==18131==    by 0x4E933AF: slapi_entry_attr_replace (entry.c:2805)
==18131==    by 0x4E9399F: slapi_entry_attr_set_charptr (entry.c:3052)
==18131==    by 0x12412060: id2entry_add_ext (id2entry.c:191)
==18131==    by 0x124430BA: modify_update_all (ldbm_modify.c:208)
==18131==    by 0x1243630F: ldbm_back_delete (ldbm_delete.c:1133)
==18131==    by 0x4E86B3F: op_shared_delete (delete.c:364)
==18131==    by 0x4E86DF2: do_delete (delete.c:128)
==18131==    by 0x41841E: connection_threadmain (connection.c:650)
==18131==    by 0x7168C2A: ??? (in /usr/lib64/libnspr4.so)
==18131==    by 0x77A7EE4: start_thread (in /usr/lib64/libpthread-2.18.so)
==18131==    by 0x7AB1D1C: clone (in /usr/lib64/libc-2.18.so)

Replication was enabled when the leak was spotted, but not sure if replication is necessary to reproduce the leak.


This was a false positive. This leak was captured from a core file after the server crashed. Running the same test without the modrdn's that crash the server(see ticket 48132), there is no longer a leak when doing deletes.

Metadata Update from @mreynolds:
- Issue assigned to mreynolds
- Issue set to the milestone: N/A

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/1462

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Invalid)

Metadata