SUMMARY plasma-systemmonitor currently only shows the memory usage of the pycharm.sh script, which is a shell script that starts the actual JVM and loads Pycharm in a subprocess. STEPS TO REPRODUCE 1. Open Pycharm 2. Open plasma system monitor 3. OBSERVED RESULT System monitor shows memory usage of only the shell script. EXPECTED RESULT System monitor shows memory usage of the whole Pycharm's process tree. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.21 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Kernel Version: 5.8.0-50-generic OS Type: 64-bit ADDITIONAL INFORMATION The script does not use "exec" to replace the script process with the JVM process. If I manually edit the script to use "exec", then system monitor will show the memory usage correctly.
*** 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.