[hardy] Resources tab of g-s-m uses 100% CPU

Bug #190120 reported by Tony Yarusso
4
Affects Status Importance Assigned to Milestone
gnome-system-monitor (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gnome-system-monitor

Running Hardy with gnome-system-monitor 2.21.5-0ubuntu1, linux kernel 2.6.24-5-generic.

There is something about the new graphs in the system monitor that cause it to use an extraordinary amount of processing power when viewed. Opening the program itself does not cause any ill effects, and the System, Processes, and File Systems tabs all work fine. However, as soon as I switch to the Resources tab my processor usage shoots up to 100%. I can confirm that it is in fact using that much, and not merely misreporting, as a) I have the system monitor panel applet running as well, and b) system responsiveness grinds to a near-halt. Switching back to one of the other three tabs makes everything normal again.

I have been using a graph refresh rate of 1/1.75s. Using 1/4.00s CPU usage drops to 50-55%. Increasing the interval to 60.00s brings it down to an almost reasonable 10%. The shortest interval that will consistently give 100% is 2.00s.

My hardware consists of a 1.86 GHz Pentium M processor and 1024 MB RAM with and ATI Radeon Mobility X300 video card.

I have attached a screenshot of the graphs, showing the result of alternating between the Resources tab and the others (as it still graphs in the background as long as the app is open). Note that actually calculating the graphs doesn't seem to be a problem, but only if you are actually looking at them.

I see that there are a number of performance-related bugs filed against g-s-m, but after looking through them it does not seem to me that any of them are the same set of conditions and symptoms, so I think this is a new bug, but am not 100% sure.

Revision history for this message
Tony Yarusso (tonyyarusso) wrote :
Revision history for this message
Murat Gunes (mgunes) wrote :

Thanks for your report. This problem has been reported as bug #187383 and I've marked your bug as a duplicate of it. You may want to add the unique information you have regarding the problem to that report.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.