After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 729710 - Wrong CPU graph
Wrong CPU graph
Status: RESOLVED DUPLICATE of bug 728644
Product: system-monitor
Classification: Core
Component: general
3.12.x
Other Linux
: Normal normal
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2014-05-07 12:31 UTC by Andrew Stubbs
Modified: 2014-05-07 14:01 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screenshot (91.93 KB, image/png)
2014-05-07 12:32 UTC, Andrew Stubbs
Details

Description Andrew Stubbs 2014-05-07 12:31:19 UTC
See the attached screenshot.

The system monitor CPU graph does not match what the textual % says. I know that the graph does smooth out some spikes, but I watched this for some time, and the text was quite steady at 90% across all CPUs.

The lines on the graph are also suspiciously evenly spread.

I noticed this when my desktop started stuttering a lot (delays in the UI, and stuttering video). Using "top" reveals that this might be because Xorg had run out of headroom - it was running at 80/90% CPU, whereas normally it uses about 20%. I don't know what the cause of that might be, but the stuttering seems to coincide with the evenly spread lines. Having a compile running in the background appears to trigger the problem, although why 1 CPU at 100% should affect the other 3 I don't know.

However, even when the machine is essentially idle the graph still looks wrong. Even when nothing else is going on, "top" shows Xorg running at 20%, and System Monitor also shows CPU1 hovering around 20%, but all the lines on the graph hover around 10%. Just to be sure, I maximised the window to enlarge the graph, and still the lines are clearly well below 20%.

This is on an 4-core, 2.2GHz Corei7 (8 with hyperthreading), running Gnome 3.12, Xorg 1.15.1, and Kernel 3.14.1.
Comment 1 Andrew Stubbs 2014-05-07 12:32:10 UTC
Created attachment 276067 [details]
Screenshot
Comment 2 Robert Roth 2014-05-07 12:50:24 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 728644 ***
Comment 3 Andrew Stubbs 2014-05-07 13:31:09 UTC
OK, I built 3.13.1 and it does appear fixed. :-)

Will there be a 3.12.2, or something? It seems wrong that I wouldn't have seen this update until 3.14 had I not gone out of my way to look for it.
Comment 4 Robert Roth 2014-05-07 13:50:16 UTC
Yes, there will be a 3.12.2, with release prepared next Monday (May 12th) and relased with the GNOME update, scheduled for May 14th.

You can always check the GNOME Schedule page[1] to find out when the next stable/unstable release is due.

[1] https://wiki.gnome.org/Schedule
Comment 5 Andrew Stubbs 2014-05-07 14:01:50 UTC
Excellent! Thanks.