Bug 377666 - Memory history doesn't match actual RAM usage
Summary: Memory history doesn't match actual RAM usage
Status: RESOLVED WORKSFORME
Alias: None
Product: ksysguard
Classification: Applications
Component: ksysguard (show other bugs)
Version: 5.9.3
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-15 22:31 UTC by Tomsk
Modified: 2019-04-10 04:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
stress (572.89 KB, image/png)
2017-03-15 22:31 UTC, Tomsk
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tomsk 2017-03-15 22:31:51 UTC
Created attachment 104589 [details]
stress

Hello,

I made a stress test for RAM and I monitored it using KSysGuard, Gnome System Monitor and Mate System Monitor. As you can see on attachment, Gnome System Monitor and Mate System Monitor shows true value (RAM full and SWAP too), at that point OS froze and not responded for any inputs. 

But KSysGuard froze at usage 1.7GB. So KSysGuard is showing 200MB-300MB less RAM usage than is actual RAM usage.
Comment 1 Tomsk 2017-06-13 20:02:43 UTC
What is status of this bug? (That KSysGuard never show 100% memory allocation)
Comment 2 Tomsk 2017-07-19 10:35:06 UTC
Here is example that KSysGuard never shows 100% RAM usage:

http://i.imgur.com/kPKK0Sn.png

All system monitors (Gnome and Mate) shows 100% RAM usage (swappiness was set to 0) and you can see that I had really 100% RAM usage because of swapping, but KSysGuard shows that I have some RAM left.
Comment 3 Richard Llom 2019-03-11 12:32:02 UTC
Tomsk, I cannot reproduce this bug.
Is this still happening on your system?
Comment 4 Bug Janitor Service 2019-03-26 04:33:09 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2019-04-10 04:33:12 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!