Bug 487200

Summary: system monitor cannot show chrome cpu and mem usages
Product: [Applications] plasma-systemmonitor Reporter: rosswzyang
Component: generalAssignee: KSysGuard Developers <ksysguard-bugs>
Status: RESOLVED WORKSFORME    
Severity: normal CC: ahiemstra, plasma-bugs-null
Priority: NOR    
Version First Reported In: 6.0.4   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description rosswzyang 2024-05-18 19:35:01 UTC 
***
system monitor cannot show chrome cpu and mem usages
***

SUMMARY
system monitor cannot show chrome cpu and mem usages


STEPS TO REPRODUCE
1. install chrome from official wensite
2.  open chrome
3. open system monitor

OBSERVED RESULT
system monitor cannot show chrome cpu and mem usages


EXPECTED RESULT
system monitor can show chrome cpu and mem usages


SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
Kernel Version: 6.8.9-300.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7735HS with Radeon Graphics
Memory: 27.1 GiB of RAM
Graphics Processor: AMD Radeon Graphics
Manufacturer: LENOVO
Product Name: 83AS
System Version: XiaoXinPro 16 ARP8

ADDITIONAL INFORMATION
Comment 1 Arjen Hiemstra 2024-05-28 13:54:35 UTC 
"chrome" is not really a single process but a collection of processes these days. So you'll have to be a bit more specific, does it not show usage in the Applications page? And does nothing show up on the Processes page either for things like its rendering processes?

If it's only the first, then there's something wrong with its CGroup and we cannot detect which processes are part of the application.

If it's the second, you'll need to do some more digging and find the PID of one of Chrome's processes, then see if `cat /proc/$PID/stat` provides any output.
Comment 2 Bug Janitor Service 2024-06-12 03:46:47 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 2024-06-27 03:47:59 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!