Bug 260732

Summary:	Tree view does not take child memory into account
Product:	[Unmaintained] ksysguard	Reporter:	Todd <toddrme2178>
Component:	general	Assignee:	KSysGuard Developers <ksysguard-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	johnflux
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Todd 2010-12-19 21:03:01 UTC

Version:           unspecified (using KDE 4.5.85) 
OS:                Linux

When you are using the tree view for the process list, each node takes into account the total processor load for all of its children.  So if a given process was using 1%, and had two child processes using 5% each, the parent will show 11% in tree view.  This also works when sorting, so the parent will be placed above an entry that has 10% load, since it is sorted based on the 11% not the 1%.

It does not do this with memory, however.  So if you have a parent using 1M, and two children each using 100M, the parent will only show 1M, not 201M.  Further, sorting also does not work correctly.  The parent is place below a process using 2M because it is sorted based on 1M not 201M.  

Reproducible: Always




This happens both in the full program and the krunner mini-version

Comment 1 Todd 2011-07-31 08:15:44 UTC

Still present in KDE 4.7.

Comment 2 John Tapsell 2011-07-31 18:39:31 UTC

I don't think I can do much with this.  It's hard to know how to add memory together, but it's very likely that the parent and child processes are sharing memory.

Comment 3 Andrew Crouthamel 2018-11-06 15:17:44 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Comment 4 Andrew Crouthamel 2018-11-18 03:33:05 UTC

Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!

Comment 5 Justin Zobel 2022-12-21 23:58:30 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 6 Bug Janitor Service 2023-01-05 05:25:18 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 7 Bug Janitor Service 2023-01-20 05:08:38 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!