| Summary: | plasma-systemmonitor shows wrong memory usage of shell script app that spawns subprocess | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] ksystemstats | Reporter: | Lê Hoàng Phương <lehoangphuongbg> |
| Component: | General | Assignee: | KSysGuard Developers <ksysguard-bugs> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | ahiemstra, kde, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
pycharm in plasma-systemmonitor applications page
pycharm in plasma-systemmonitor processes page pycharm in ksysguard systemd-cgls output |
||
|
Description
Lê Hoàng Phương
2021-04-19 02:28:12 UTC
*** Bug 435900 has been marked as a duplicate of this bug. *** On which page? Can you include a screenshot? Created attachment 137747 [details]
pycharm in plasma-systemmonitor applications page
Created attachment 137748 [details]
pycharm in plasma-systemmonitor processes page
Created attachment 137749 [details]
pycharm in ksysguard
In applications page, the memory usage is only for the shell script. In processes page, if I filter by "pycharm", it doesn't show the subprocess of the shell script. I attached the screenshot of pycharm in ksysguard for comparison. Ksysguard shows all the subprocesses of pycharm correctly. plasma-systemmonitor should show the same in the processes page if you switch to tree style. That said, please provide the output of `systemd-cgls` when running pycharm, that will provide more information about what's going wrong in the applications page. Created attachment 137780 [details] systemd-cgls output Here is the output of systemd-cgls when running pycharm. > plasma-systemmonitor should show the same in the processes page if you switch to tree style The screenshot that I uploaded was taken with tree style. Though it seems the filter behavior of this tree is not what I expected. If a parent item matches with the filter keyword, its children should be not be filtered again. But this now becomes off-topic. |