Bug 1281276

Summary: free -h segfaults with obscene amount of memory
Product: [Fedora] Fedora Reporter: Tomasz Torcz <tomek>
Component: procps-ngAssignee: Jaromír Cápík <jaromir.capik>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: ovasik
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:27:46 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 Tomasz Torcz 2015-11-12 08:39:52 UTC
Description of problem:
Starting program: /usr/bin/free -h
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
              total        used        free      shared  buff/cache   available

Program received signal SIGSEGV, Segmentation fault.
scale_size (size=18446744073707252340, flags=flags@entry=2, args=...) at free.c:145
145             for (i = 1; up[0] != '0'; i++, up++) {


Without "-h":
              total        used        free      shared  buff/cache   available
Mem:    9007199254740988    -2318312 9007199254738032      198248     2321268    12563592
Swap:      16777212     4648976    12128236




Version-Release number of selected component (if applicable):
procps-ng-3.3.10-8.fc22.x86_64



Additional info:
    Virtualization: lxc-libvirt

Comment 1 Fedora End Of Life 2016-07-19 18:27:46 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.