Bug 434039 - Memory details are missing
Summary: Memory details are missing
Status: RESOLVED WORKSFORME
Alias: None
Product: plasma-systemmonitor
Classification: Applications
Component: general (show other bugs)
Version: 5.21.2
Platform: Gentoo Packages Linux
: NOR major
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-06 01:51 UTC by Nicolas Werner
Modified: 2021-11-11 01:21 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Memory details view in Ksysguard (459.16 KB, image/png)
2021-03-06 01:51 UTC, Nicolas Werner
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Werner 2021-03-06 01:51:41 UTC
Created attachment 136422 [details]
Memory details view in Ksysguard

SUMMARY

KSysguard used to provide detailed memory information about where and what memory is used. While it is unfortunate, that this was rendered in a WebView, this view alone is my primary reason for using KSysguard. Since KSysguard is going to be replaced (I'm told), systemmonitor should provide the same or an equivalent view.

You can find the view in Ksysguard by going to the process view and right clicking on a process.

OBSERVED RESULT

No memory detail view in the replacement for KSysguard.

EXPECTED RESULT

A memory detail view, that is at least as powerful as the tool, that it is intended to replace.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.21.2
KDE Frameworks Version: 5.79.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

KSysguard is always the first KDE tool I install on a new system, specifically, because the memory overview is much more powerful than tools like htop provide. I really don't want to use one of my most used features, just to make a nicer looking tool.
Comment 1 Arjen Hiemstra 2021-03-08 11:26:34 UTC
What's your use case? One of the reasons we did not add it is that we did not know an actual usecase that isn't solved better by some dedicated tool. If you have a usecase though, we may reconsider that.
Comment 2 Bug Janitor Service 2021-03-23 04:33:45 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 3 Bug Janitor Service 2021-04-07 04:33: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!
Comment 4 Nicolas Werner 2021-11-11 01:21:48 UTC
I'm sorry that I didn't reply originally. I had my email set to an old address and forgot about it.  I'm very happy to see, that the memory view was kept though! So I think my reply is not really necessary, but I'll add it anyway:

I do agree, that a dedicated application would probably make more sense, but I haven't found one yet, that displays that information in such a concise and easy to access manner. I usually use it to quickly figure out, where an application is using memory, since I have a lot of applications, that memory map files and seeing what is dirty, what are libraries, etc is very useful to me. It is also very useful, that one can see what files an application has loaded into memory, which can be used to figure out what libraries an application has still loaded into memory, what database it has open and more. It mostly became a habit to look there, because I am used to that view existing. I know, there are other ways to do that, but they are either not as convenient or I don't have the muscle memory for it. Thank you very much for keeping it around, I hope it isn't too big of a burden to maintain!