| Summary: | kioslave5 consumes massive resources slowing down Gimp file save 10 times | ||
|---|---|---|---|
| Product: | [Frameworks and Libraries] frameworks-kio | Reporter: | BWK <blackwhitekez> |
| Component: | general | Assignee: | KIO Bugs <kio-bugs-null> |
| Status: | REOPENED --- | ||
| Severity: | normal | CC: | a.samirh78, kdelibs-bugs-null, kfm-devel, nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.92.0 | ||
| Target Milestone: | --- | ||
| Platform: | Kubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Partial output in terminal | ||
|
Description
BWK
2022-05-09 14:25:21 UTC
From terminal enabled kio debug output, and start dolphin: export QT_LOGGING_RULES="*kio*=true" dolphin then save in gimp, and attach the terminal output here, hopefully it'll give a clue what's going on. 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! 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! The issue is most apparent when Dolphin is monitoring the folder in which the file is being saved into. Otherwise, the operation is unremarkable. This can be seen occurring in real time. With the Dolphin window showing any other folder, the multiple running instances of kioslave5 are totalling well under 1 Gb of memory. As soon as the folder in which the file is being saved into is entered from the Dolphin window, there is an immediate appearance of an instance of kioslave5 with the behaviour described above. Created attachment 151699 [details]
Partial output in terminal
Comment on attachment 151699 [details]
Partial output in terminal
Also seeing this issue on a different computer that has a Dolphin window open that was browsing to the same file path through a NFS share, kioslave5 on this computer behaving in the same way during save even though the save operation is not occurring there.
|