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 130081 - Sorting processed by %CPU does not work when "Process Dependancies" is on
Sorting processed by %CPU does not work when "Process Dependancies" is on
Status: RESOLVED OBSOLETE
Product: system-monitor
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
: 127714 564037 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-12-27 15:52 UTC by Sebastien Bacher
Modified: 2018-05-22 11:56 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sebastien Bacher 2003-12-27 15:52:12 UTC
This bug was originally reported in the Debian BTS:
http://bugs.debian.org/216436

'"I saw this bug when running nautilus with the tree view in the left pane
which caused fam to use 82% system CPU as shown by the 'top' program.  The
gnome-panel system monitor applet also showed high system CPU use but
asking gnome-system-monitor to sort processes by %CPU showed
gnome-system-monitor itself as the highest user at about 5%.

If I used the search field to search for fam, fam was then highlighted and
shown correctly as using 82% CPU but it wasn't at the top of the list or
indeed anywhere near the top.  I could only get fam to the top of the list
by turning off the "Process Dependencies" option."

"If I turn on "View Process Dependencies" from the view menu the CPU
sorting becomes broken.  What seems to have is that the top level
processes, i.e. those whose parent is PID 1 (init) get sorted by CPU
utilization and the all other processes are simply displayed under  
their parent process.
This algorithm isn't useful as processes using too much CPU don't
necessarily need to have init as their parent.

The algorithm I suggest instead is that a separate, CPU figure is used for
sorting which for top level process is sum of it's own direct utililastion
and the the equivalent firgure for each of it's children recursively.

The same algorithm would need to be implemented for memory too when the
dependency view is turned on.

If I turn off the process dependency view, sorting works correctly."


I'm not sure but this bug is perhaps related to #85388
Comment 1 Robert Roth 2011-12-19 01:36:10 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 127714 ***
Comment 2 Martin Erik Werner 2011-12-19 21:31:10 UTC
This is *not* a duplicate of bug 127714, this bug is a request for a change to the behaviour of the dependency view, and not a request for greater obviousness with regards to the options.

Instead of current view/sorting:

process  ^foo usage
c        3
d        2
a        1
 \        
  b      5

(b is a child of a)

It is a request for a view/sorting like:

process  ^foo usage
a        1+5=6
 \        
  b      5
c        3
d        2

Here "foo" can be memory, cpu, or any other metric that can sanely be summed to a total which has a meaning (i.e. not pid, I guess).

So, the feature request is for dependency parents to be assigned, and hence be sortable by, the sum total of the attribute of itself, and all of its' dependency children.
Comment 3 Robert Roth 2011-12-20 08:38:04 UTC
Thanks for clarifying this, this problem is also reported already, but as that one is a newer bug, I am reopening this (unmarking it from a duplicate) and marking the other one as a duplicate of this.
Comment 4 Robert Roth 2011-12-20 08:38:20 UTC
*** Bug 564037 has been marked as a duplicate of this bug. ***
Comment 5 Robert Roth 2012-12-06 12:05:54 UTC
*** Bug 127714 has been marked as a duplicate of this bug. ***
Comment 6 GNOME Infrastructure Team 2018-05-22 11:56:18 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-system-monitor/issues/2.