Bug 487752 - System monitor stalls while trying to show super long "Command" popup
Summary: System monitor stalls while trying to show super long "Command" popup
Status: REPORTED
Alias: None
Product: plasma-systemmonitor
Classification: Applications
Component: general (show other bugs)
Version: 6.0.4
Platform: Manjaro Linux
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-05-29 16:43 UTC by mirh
Modified: 2024-06-30 22:22 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mirh 2024-05-29 16:43:09 UTC
SUMMARY
I was trying to monitor a pesky bug with Ark, when I wanted to see the parameters of its stuck "unar" sub-process to replicate it from CLI. This turned into yet another issue discovered. 

STEPS TO REPRODUCE
1. Have the column "Command" shown
2. Move the mouse arrow on top of some process with a very long one

OBSERVED RESULT
An excruciating amount of time passes, and only then will the popup come out. 
Once it even glitched again after a few seconds, with the popup disappearing into a tiny empty rectangle and I believe plasma-systemmonitor taking north of 1GB of ram (I couldn't tell the process names on the left column that I had scrolled away, but "something" had crossed that threshold that previously wasn't there)

EXPECTED RESULT
Don't hang and go crazy. 

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux 
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.6.30-2-MANJARO (64-bit)
Graphics Platform: X11
Comment 1 Nate Graham 2024-06-12 19:35:57 UTC
I can't reproduce this with a command for Discord in a Flatpak, which is absurdly long.
Comment 2 mirh 2024-06-13 19:58:46 UTC
I'm skeptical that would be any near even the same order of magnitude of Ark somehow passing every single file inside the folder that I wanted to extract to the external command. 
I don't have the exact figures at hands, but "thousands" would probably just be their number. Then you have to take into account their full path.
Comment 3 Nate Graham 2024-06-14 20:35:12 UTC
Can you provide fuller steps to reproduce that include downloading or generating an appropriate archive?
Comment 4 Bug Janitor Service 2024-06-29 03:47:28 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 5 mirh 2024-06-30 22:22:19 UTC
Uhm, well.. Let's say that I was tinkering with a 19GB rar file containing the source code tree of a famous graphics card manufacturer. 
So maybe you could try with more or less the same setup (Ark, rar, extract some deep folder) and an archive with the gecko or linux repositories? If that still doesn't work perhaps you could try to rename the many sub-folders to something a bit more comically longer.