Bug 428823 - CPU usage y-axis go above 100%
Summary: CPU usage y-axis go above 100%
Status: RESOLVED FIXED
Alias: None
Product: plasma-systemmonitor
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Other Other
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
: 428822 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-11-08 07:27 UTC by Andy Great
Modified: 2021-02-05 09:49 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
CPU usage y-axis go above 100% (647.77 KB, image/png)
2020-11-08 07:28 UTC, Andy Great
Details
ksysguard show proper CPU usage while system monitor does not. (176.40 KB, image/png)
2020-11-08 07:36 UTC, Andy Great
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andy Great 2020-11-08 07:27:54 UTC
CPU usage y-axis go above 100%

STEPS TO REPRODUCE
I am not even sure how it get like this, it appears to happen randomly.

OBSERVED RESULT
CPU usage y-axis go above 100% and went to 800%. This make the CPU usage look flat because it is so small.

EXPECTED RESULT
The CPU usage should not go above 100%

I install system monitor from here: https://build.opensuse.org/package/show/KDE:Frameworks5/plasma5-systemmonitor

System monitor 1.0
Operating System: openSUSE Tumbleweed 20201105
KDE Plasma Version: 5.20.2
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1
Kernel Version: 5.9.1-1-default
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-3770 CPU @ 3.40GHz
Memory: 7.5 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4000
Comment 1 Andy Great 2020-11-08 07:28:09 UTC
Created attachment 133131 [details]
CPU usage y-axis go above 100%
Comment 2 Andy Great 2020-11-08 07:35:39 UTC
Update: It seems that 800% CPU on y-axis is not an issue, the issue is that the CPU usage is shown as 0%.

Try using ksysguard which show CPU usage properly.

I upload a new screenshot showing system monitor on the left and ksysguard on the right.
Comment 3 Andy Great 2020-11-08 07:36:31 UTC
Created attachment 133132 [details]
ksysguard show proper CPU usage while system monitor does not.
Comment 4 Justin Zobel 2020-11-08 09:36:44 UTC
Was this reported twice, here and 428822?
Comment 5 2wxsy58236r3 2020-11-08 10:46:00 UTC
*** Bug 428822 has been marked as a duplicate of this bug. ***
Comment 6 Andy Great 2020-11-08 12:49:48 UTC
(In reply to Justin Zobel from comment #4)
> Was this reported twice, here and 428822?

Yes, I don't know why it was posted twice.
Comment 7 Arjen Hiemstra 2020-11-08 13:37:02 UTC
The 800% value is because the chart is stacked so each individual core is added up. Since each core ranges from 0 to 100% and you have 8 cores you end up with 800%. We solved this for the process/applications table by having a way to display values normalized to 100%, we might want to do something similar here but that's a bit more tricky.

As to why it is showing only 0%, that one is a bit more odd as the sensors use the same data source. Does the "CPU" chart on the overview page work correctly?
Comment 8 Andy Great 2020-11-08 14:38:13 UTC
(In reply to Arjen Hiemstra from comment #7)
> The 800% value is because the chart is stacked so each individual core is
> added up. Since each core ranges from 0 to 100% and you have 8 cores you end
> up with 800%. We solved this for the process/applications table by having a
> way to display values normalized to 100%, we might want to do something
> similar here but that's a bit more tricky.
> 
> As to why it is showing only 0%, that one is a bit more odd as the sensors
> use the same data source. Does the "CPU" chart on the overview page work
> correctly?

I get the 800% CPU usage now. I will have to wait until CPU usage is 0% again because I reboot my PC and its fixed, it happen randomly for some reason.
Comment 9 Bug Janitor Service 2020-11-23 04:34:12 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 10 Christoph Feck 2020-12-01 12:08:08 UTC
New information was added with comment 8; changing status for inspection.
Comment 11 David Redondo 2020-12-03 08:16:59 UTC
Just for future refrence, if one prefers the way it is displayed in ksysguard they can uncheck "Stacked Charts" and lower the "Fill Opacity" in the chart settings.
Comment 12 David Redondo 2021-02-05 09:49:18 UTC
Seems like this is resolved now, if you encounter it again feel free to reopen or file a new bug.