Exeptionally high CPU consumption
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-system-monitor (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gnome-system-
Step to reproduce:
1. click on the System Monitor, notice that a window with CPU usage charts opens up
2. the CPU usage quickly grows. On 4 CPU machine is raises from a few percents to about 50% in about a minute and then stays on that level. The CPU usage is caused by Gnome System Monitor. It also seems to be proportional to the amount of space occupied by the chart (the part with lines), which may point to inefficiencies in plotting the chart.
3. closing down the window with chart returns the CPU consumption back to normal (1-2 percents) but minimizing the windows does not change anything.
Screenshot is attached.
Why this is a problem:
This application is supposed to provide information on CPU usage by other applications. The fact that it uses such vast amounts of CPU power itself completely skews the picture and makes the measurements useless: instead of seeing what applications are doing one can only see that the computer's CPU is overloaded by the monitoring. It is not just bad. It is worse than that. :-(
Expected behaviour:
CPU usage of the application must be negligible. The problem of drawing a few lines was never a big deal even on 20MHz machines.
Description: Ubuntu 10.10
Release: 10.10
Installed: 2.28.1-1ubuntu1
Candidate: 2.28.1-1ubuntu1
Version table:
*** 2.28.1-1ubuntu1 0
500 http://
100 /var/lib/
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: gnome-system-
ProcVersionSign
Uname: Linux 2.6.35-24-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Fri Jan 21 20:22:25 2011
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcEnviron:
LANG=en_GB.utf8
SHELL=/bin/bash
SourcePackage: gnome-system-
I noticed this too. When I use top in a terminal, it shows top using minimal, and gnome-system- monitor avg of 35%. In one instance, ntop used 100% CPU. I issue a 'killall ntop' and then the high CPU usage dropped away, but can't say if this was related. Will do some more checks.