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 753731 - Unreliable cpu detection through glibtop
Unreliable cpu detection through glibtop
Status: RESOLVED FIXED
Product: system-monitor
Classification: Core
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2015-08-17 18:05 UTC by Helio Chissini de Castro
Modified: 2015-09-01 19:56 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Path to use proprer sysconf (1.82 KB, patch)
2015-08-17 18:05 UTC, Helio Chissini de Castro 		none Details | Review

Description Helio Chissini de Castro 2015-08-17 18:05:46 UTC 
Created attachment 309407 [details] [review]
Path to use proprer sysconf

glibtop not provides the number of cpus on the machine directly, relying on a list with the current load of each core.

Original code assume that a 0 load core is the end of cpu list, which is invalid in cases of machines with high number of cores, that happens to some cores stay idle with 0 load.

Since this can happens in any core number, if a machine has 192 cores, but the core number 5 has 0 load, then 4 cores will be wrongly reported.

Using standard sysconf api solves the issue in a simple way.
Comment 1 Benoît Dejean 2015-08-21 19:57:50 UTC 
I'm not sure about how standard sysconf is. But glibtop_get_sysinfo() works.
So how about this: https://git.gnome.org/browse/gnome-system-monitor/commit/?id=549e2e3308620810dd795321d02f041e8ab58d29 ?
Comment 2 Robert Roth 2015-09-01 19:56:53 UTC 
This problem has been fixed in the unstable development version. The fix will be available in the next major software release. You may need to upgrade your Linux distribution to obtain that newer version.