Bug 1725786 - Memory leak in libgfortran
Summary: Memory leak in libgfortran
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gcc
Version: 8.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: 8.0
Assignee: Marek Polacek
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-01 12:57 UTC by Paulo Andrade
Modified: 2023-07-18 14:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-01 19:26:37 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.