RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

[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.