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 309839 - Processes list should be completely idle if window not mapped
Processes list should be completely idle if window not mapped
Status: RESOLVED FIXED
Product: system-monitor
Classification: Core
Component: general
2.10.x
Other Linux
: Normal normal
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2005-07-08 20:16 UTC by Raul Acevedo
Modified: 2014-02-06 00:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Description Raul Acevedo 2005-07-08 20:16:30 UTC 
Distribution/Version: Fedora Core 4

The processes list should be completely idle if the window is not mapped.  Via
top, I can see that even if system-monitor is iconified or not visible on a
different desktop, it still uses up on average 3-5% CPU.  I have set the graphs
to update every 60 seconds and devices every 90 second, process list every 3
seconds.

The idea is that I want to keep it running in the background, using up no CPU,
but when I map or view the window, the process list should update.  (I'm filing
a separate bug to completely disable the graphs/devices tab, since I really
don't care about that, I just want a visual version of top.)
Comment 1 Benoît Dejean 2005-12-27 10:54:13 UTC 
Sorry for responding that late. I kept your bug in mind.

There are 3 notebook pages :
- processes : maybe the most CPU consuming. Getting processes stats and updating the processes list are mixed in code. It may need deep rework.
- resources : already have a load_graph_stop() to prevent graphs from being drawn again. But still acquiring data in background
- disklist : not expansive at all. IIRC, default interval is 30s. nothing to do here
Comment 2 Robert Roth 2014-02-06 00:27:40 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.