Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 1725786

Summary: Memory leak in libgfortran
Product: Red Hat Enterprise Linux 8 Reporter: Paulo Andrade <pandrade>
Component: gccAssignee: Marek Polacek <mpolacek>
gcc sub component: system-version QA Contact: qe-baseos-tools-bugs
Status: CLOSED NEXTRELEASE Docs Contact:
Severity: medium    
Priority: medium CC: ahajkova, fweimer, jakub, ohudlick
Version: 8.2   
Target Milestone: rc   
Target Release: 8.0   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-01 19:26:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Paulo Andrade 2019-07-01 12:57:45 UTC
Reproducer:

"""
$ cat /tmp/open_leak.f90
program open_leak
  implicit none

  open (unit = 6, &
    file = "/tmp/open_leak.f90", &
    status = 'OLD')

  close (unit = 6)
end program open_leak

$ gfortran -fsanitize=address -Wall -Wextra -pedantic /tmp/open_leak.f90 -o /tmp/open_leak; /tmp/open_leak 

=================================================================
==26750==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 32 byte(s) in 1 object(s) allocated from:
    #0 0x7f5c5fc8f768 in __interceptor_malloc (/lib64/libasan.so.5+0xef768)
    #1 0x7f5c5f7435c8 in _gfortrani_xmalloc ../../../libgfortran/runtime/memory.c:42

Indirect leak of 512 byte(s) in 1 object(s) allocated from:
    #0 0x7f5c5fc8f768 in __interceptor_malloc (/lib64/libasan.so.5+0xef768)
    #1 0x7f5c5f7435c8 in _gfortrani_xmalloc ../../../libgfortran/runtime/memory.c:42

SUMMARY: AddressSanitizer: 544 byte(s) leaked in 2 allocation(s).
"""

  This should be fixed by the first chunk of the patch
https://gcc.gnu.org/viewcvs/gcc/trunk/libgfortran/io/open.c?r1=267910&r2=267909&pathrev=267910
indirectly fixed by  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88776
[Namelist read from stdin: loss of data]

Comment 1 Marek Polacek 2019-07-01 18:56:27 UTC
This bug report doesn't specify the version of gcc you are using.

The fix appears to be in gcc-8.3.1-4.4.el8 already.

Comment 2 Paulo Andrade 2019-07-01 19:26:37 UTC
Thanks for checking.

It was tested with latest released version.

Confirmed to be fixed in gcc-8.3.1-4.4.el8.