Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#56356 - procps-ng (top) memory reporting is incorrect.

Attached to Project: Arch Linux
Opened by Lawrence Ott (AvnSgt) - Thursday, 16 November 2017, 21:12 GMT
Last edited by Eli Schwartz (eschwartz) - Friday, 17 November 2017, 04:00 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The following bug was observed on a mid 2009 - Macbook Pro running ArchLabs, with an Arch Core package.
When executing the "top" command, the memory field reports:
GiB Mem :487057143103488.0/3.612

To verify this, "free -h" and "htop" were both executed separately to compare to the output of top.
Neither "free" or "htop" are affected, and they are both reporting correctly.

The installed version of "procps-ng" is 3.3.12-1
The environment: i3, with gaps, and rofi,
Shell: bash 4.4.12
The terminal: termite
Linux kernel: 4.13.12-1
Applications Running: FireFox 57 multiple tabs, Riot, Wire, Termite, Enpass

See the attached image to verify Memory issue.
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Friday, 17 November 2017, 04:00 GMT
Reason for closing:  Works for me
Additional comments about closing:  ArchLabs is not Arch Linux
Comment by Lawrence Ott (AvnSgt) - Friday, 17 November 2017, 00:30 GMT
On reboot a new snapshot was taken.
Top output:
---------------------
GiB Mem : 20.0/3.612

Htop output:
---------------------
Mem: 904M/3.61G

free -h output:
---------------------------------------------------------------------------------
total used free shared buff/cache available
Mem: 3.6G 867M 2.2G 28M 559M 2.7G
Swap: 7.9G 0B 7.9G

Top's reporting memory in use is off.
Comment by Lawrence Ott (AvnSgt) - Friday, 17 November 2017, 00:43 GMT
Prior to launching Riot.IM desktop messaging client top's behavior is fairly normal, even though the memory statistic is off. However, after launching Riot.IM, this memory spike was captured once again.

WM: i3
Shell: Bash
Terminal: Termite
Applications launched include:

i3-gapps, polybar, rofi, firefox quantum, Riot

shutter was used to capture top's error.

Loading...