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

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)

Thanks Noriko!

99f9974..d2dfda9 master -> master
commit d2dfda9
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 bc47239

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

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 2444e0c

Coverity issue reported, reopening...

7aeeb7c..1553b66 master -> master
commit 1553b66
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 af163d3

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

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 ea01c96

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

4 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/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)

a year ago

Login to comment on this ticket.