This bug is created as a clone of upstream ticket:
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)
 setup DS using valgrind
 Add 2 COS templates and definitions
 Modify the template in any way
 stop theserver and check the valgrind output file for "cos_cache_add_attrval"
 If it's not found the leak is fixed.
[root@qe-blade-09 export]# ldapmodify -x -a -D "cn=Directory Manager" -w Secret123 -p 389 -h localhost -f /export/1169975COS.ldif
adding new entry "cn=cosTemplateExample,ou=People,dc=example,dc=com"
adding new entry "cn=cosTemplateExample1,ou=People,dc=example,dc=com"
adding new entry "cn=cosPointer,ou=People,dc=example,dc=com"
adding new entry "cn=cosPointer1,ou=People,dc=example,dc=com"
[root@qe-blade-09 export]# ldapmodify -x -D "cn=Directory Manager" -w Secret123 -p 389 -h localhost << EOF
modifying entry "cn=cosTemplateExample,ou=People,dc=example,dc=com"
[root@qe-blade-09 export]# service dirsrv stop
Shutting down dirsrv:
there is no memory leak for COS, but there are other leaks. PFA for the valgrind output and suggest, if they required to be fixed.
I am marking this bug as VERIFIED as no leaks for COS found.
Created attachment 998213 [details]
You can mark this as verified. There are other virtual attribute search leaks, but there is already a ticket open for those. The rest of the leaks can be ignored and are harmless (startup) leaks.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.