#48168 memory leak in uniqueness plugin if it fails to start
Closed: wontfix None Opened 9 years ago by mreynolds.

==10418== Thread 1:
==10418== 52 bytes in 5 blocks are definitely lost in loss record 701 of 1,508
==10418==    at 0x4C2B946: calloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==10418==    by 0x4E8A136: slapi_ch_calloc (ch_malloc.c:243)
==10418==    by 0xEF64BA4: uniqueness_entry_to_config (uid.c:370)
==10418==    by 0xEF667EB: uiduniq_start (uid.c:1383)
==10418==    by 0x4EED8E0: plugin_call_func (plugin.c:1949)
==10418==    by 0x4EED76E: plugin_call_one (plugin.c:1899)
==10418==    by 0x4EEBE63: plugin_start (plugin.c:1282)
==10418==    by 0x4EEFE64: plugin_add (plugin.c:3032)
==10418==    by 0x4E9B73D: dse_add_plugin (dse.c:2182)
==10418==    by 0x4E9C050: dse_add (dse.c:2403)
==10418==    by 0x4E7ECB3: op_shared_add (add.c:740)
==10418==    by 0x4E7DBC7: do_add (add.c:258)
==10418==    by 0x4163EC: connection_dispatch_operation (connection.c:645)
==10418==    by 0x4183BC: connection_threadmain (connection.c:2534)
==10418==    by 0x6B1ACAA: ??? (in /usr/lib64/libnspr4.so)
==10418==    by 0x7159529: start_thread (in /usr/lib64/libpthread-2.20.so)
==10418==    by 0x746E77C: clone (in /usr/lib64/libc-2.20.so)
==10418==
==10418== 80 bytes in 5 blocks are definitely lost in loss record 964 of 1,508
==10418==    at 0x4C2B946: calloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==10418==    by 0x4E8A136: slapi_ch_calloc (ch_malloc.c:243)
==10418==    by 0xEF645E8: uniqueness_entry_to_config (uid.c:229)
==10418==    by 0xEF667EB: uiduniq_start (uid.c:1383)
==10418==    by 0x4EED8E0: plugin_call_func (plugin.c:1949)
==10418==    by 0x4EED76E: plugin_call_one (plugin.c:1899)
==10418==    by 0x4EEBE63: plugin_start (plugin.c:1282)
==10418==    by 0x4EEFE64: plugin_add (plugin.c:3032)
==10418==    by 0x4E9B73D: dse_add_plugin (dse.c:2182)
==10418==    by 0x4E9C050: dse_add (dse.c:2403)
==10418==    by 0x4E7ECB3: op_shared_add (add.c:740)
==10418==    by 0x4E7DBC7: do_add (add.c:258)
==10418==    by 0x4163EC: connection_dispatch_operation (connection.c:645)
==10418==    by 0x4183BC: connection_threadmain (connection.c:2534)
==10418==    by 0x6B1ACAA: ??? (in /usr/lib64/libnspr4.so)
==10418==    by 0x7159529: start_thread (in /usr/lib64/libpthread-2.20.so)
==10418==    by 0x746E77C: clone (in /usr/lib64/libc-2.20.so)

This is a regression from https://fedorahosted.org/389/ticket/48026 The friendly attributes are not freed in the close function.

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

7 years ago

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

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: Duplicate)

3 years ago

Login to comment on this ticket.

Metadata