-
Bug
-
Resolution: Unresolved
-
Normal
-
rhel-9.6
-
None
-
None
-
Important
-
rhel-idm-ds
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
When LDAP server restart, the ASAN detect following leake
================================================================= ==1415==ERROR: LeakSanitizer: detected memory leaks Direct leak of 2672 byte(s) in 57 object(s) allocated from: #0 0x7f8e372b4bd7 in calloc (/usr/lib64/libasan.so.6+0xb4bd7) #1 0x7f8e36ed631c in slapi_ch_calloc (/usr/lib64/dirsrv/libslapd.so.0+0xd631c) Direct leak of 175 byte(s) in 7 object(s) allocated from: #0 0x7f8e372b4a07 in __interceptor_malloc (/usr/lib64/libasan.so.6+0xb4a07) #1 0x7f8e36ed5228 in slapi_ch_malloc (/usr/lib64/dirsrv/libslapd.so.0+0xd5228) Indirect leak of 1040 byte(s) in 4 object(s) allocated from: #0 0x7f8e372b4a07 in __interceptor_malloc (/usr/lib64/libasan.so.6+0xb4a07) #1 0x7f8e36ed5228 in slapi_ch_malloc (/usr/lib64/dirsrv/libslapd.so.0+0xd5228) Indirect leak of 859 byte(s) in 14 object(s) allocated from: #0 0x7f8e3725baf7 in strdup (/usr/lib64/libasan.so.6+0x5baf7) #1 0x7f8e36ed6c34 in slapi_ch_strdup (/usr/lib64/dirsrv/libslapd.so.0+0xd6c34) Indirect leak of 509 byte(s) in 2 object(s) allocated from: #0 0x7f8e372b4a07 in __interceptor_malloc (/usr/lib64/libasan.so.6+0xb4a07) #1 0x7f8e37d58f24 in ber_memalloc_x (/lib64/liblber.so.2+0x6f24) Indirect leak of 160 byte(s) in 2 object(s) allocated from: #0 0x7f8e372b4bd7 in calloc (/usr/lib64/libasan.so.6+0xb4bd7) #1 0x7f8e37d59a4c in ber_memcalloc_x (/lib64/liblber.so.2+0x7a4c) SUMMARY: AddressSanitizer: 5415 byte(s) leaked in 86 allocation(s).
What is the impact of this issue to you?
Memory leak
Please provide the package NVR for which the bug is seen:
389-ds-base-2.6.1-12.3
How reproducible is this bug?:
Always
Steps to reproduce
- Start the server
Expected results
Not memory leak
Actual results
Memory leak
- is related to
-
-
- Release Pending
-
