Hide Forgot
[root@vm-asterisk04t asterisk-13.7.0]# LD_PRELOAD=/lib64/libasan.so.2 killall 11111 11111: no process found ================================================================= ==1708==ERROR: LeakSanitizer: detected memory leaks Direct leak of 1024 byte(s) in 1 object(s) allocated from: #0 0x7fe30ef15a0a in malloc (/lib64/libasan.so.2+0x98a0a) #1 0x402104 (/usr/bin/killall+0x402104) #2 0x7fff99d3e4fb (<unknown module>) Direct leak of 1024 byte(s) in 1 object(s) allocated from: #0 0x7fe30ef15a0a in malloc (/lib64/libasan.so.2+0x98a0a) #1 0x402183 (/usr/bin/killall+0x402183) Direct leak of 384 byte(s) in 3 object(s) allocated from: #0 0x7fe30ef15a0a in malloc (/lib64/libasan.so.2+0x98a0a) #1 0x402c76 (/usr/bin/killall+0x402c76) Direct leak of 4 byte(s) in 1 object(s) allocated from: #0 0x7fe30ef15a0a in malloc (/lib64/libasan.so.2+0x98a0a) #1 0x40202b (/usr/bin/killall+0x40202b) SUMMARY: AddressSanitizer: 2436 byte(s) leaked in 6 allocation(s).
used devtoolset-4 (gcc-5.2)
[root@vm-asterisk04t ~]# rpm -qa | grep libasan devtoolset-4-libasan-devel-5.2.1-2.2.el7.x86_64 libasan2-5.2.1-2.2.el7.x86_64 [root@vm-asterisk04t ~]# rpm -qa | grep psmis psmisc-22.20-9.el7.x86_64 [root@vm-asterisk04t ~]# uname -a Linux vm-asterisk04t.tcsbank.ru 3.10.0-327.4.4.el7.x86_64 #1 SMP Tue Jan 5 16:07:00 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Hello Badalyan, you're right, one of the four leaks is actually lost memory allocation. Thanks for your eagle eye! The rest is actually not lost memory, it's just not returned right before the termination of the program. I'm not sure if upstream will accept the fix. IMO it's nothing against nothing. I will propose the fix of the former to the upstream and let's see. Thanks.
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.