389-ds-base

#47969 COS memory leak when rebuilding the cache
Closed: wontfix Opened by mreynolds.

Closed: wontfix
Reopen Issue

When the COS cache is released, the schema cache is not correctly freed. We leak memory every time the cache is rebuilt.

==24017== 102 (72 direct, 30 indirect) bytes in 3 blocks are definitely lost in loss record 1,277 of 2,056
==24017==    at 0x4C2745D: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==24017==    by 0x4E854CA: slapi_ch_malloc (ch_malloc.c:155)
==24017==    by 0x111F0244: cos_cache_add_attrval (cos_cache.c:1532)
==24017==    by 0x111F2A48: cos_cache_schema_build (cos_cache.c:2751)
==24017==    by 0x111EE46B: cos_cache_create (cos_cache.c:498)
==24017==    by 0x111EE32E: cos_cache_wait_on_change (cos_cache.c:451)
==24017==    by 0x718FE3A: ??? (in /usr/lib64/libnspr4.so)
==24017==    by 0x77CEEE4: start_thread (in /usr/lib64/libpthread-2.18.so)
==24017==    by 0x7AD8B8C: clone (in /usr/lib64/libc-2.18.so)

Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1169975

Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1170708

Thanks Noriko!

99f9974..d2dfda9 master -> master
commit d2dfda95c543f106443f898436151b00c68e4270
Author: Mark Reynolds mreynolds@redhat.com
Date: Tue Dec 2 13:38:06 2014 -0500

f2df95e..bc47239 389-ds-base-1.3.3 -> 389-ds-base-1.3.3
commit bc47239c5c7e6d19564fcd2839c6f2bd81a5b540

1e61e2c..5237b21 389-ds-base-1.3.2 -> 389-ds-base-1.3.2
commit 5237b2151b6bdff8a39a9d9ff9fc2a2013fb51ab

a5d8b2c..a2fc9d4 389-ds-base-1.3.1 -> 389-ds-base-1.3.1
commit a2fc9d46b9ea2997670996d46b8aa94351c8d606

9d03dcd..2444e0c 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit 2444e0c4362615c4c65ffceeeb30d9380fb61e49

Coverity issue reported, reopening...

7aeeb7c..1553b66 master -> master
commit 1553b665bfecbbccd54c439442d9a22c5d35d4a1
Author: Mark Reynolds mreynolds@redhat.com
Date: Mon Dec 8 09:57:50 2014 -0500

8b7ae6d..af163d3 389-ds-base-1.3.3 -> 389-ds-base-1.3.3
commit af163d345b4524c121296626cb2e9da26d6d061e

80c34a5..f97e86d 389-ds-base-1.3.2 -> 389-ds-base-1.3.2
commit f97e86d6cde2de55c6ecf4a3213d6b504c4fcecc

dca0b39..ff208d6 389-ds-base-1.3.1 -> 389-ds-base-1.3.1
commit ff208d6d3681919c0be1479a47db4bb41e1090ac

90ab84c..ea01c96 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit ea01c960f0f32bead97fc3615c73f2cc3c4faba8

Metadata Update from @mreynolds:
- Issue assigned to mreynolds
- Issue set to the milestone: 1.2.11.33

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

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: Fixed)
Metadata
None
None
None
Normal
Community
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.