Summary: | kio_file: possible memory leak when copying files from smb:/ to local directory | ||
---|---|---|---|
Product: | [Unmaintained] kio | Reporter: | karl.r.ernst |
Component: | file | Assignee: | David Faure <faure> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | adawit, arjunak234, ggrabler |
Priority: | NOR | ||
Version: | 4.7 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
details of memory usage
Showing my memory usage of kio_file during a ssh copy via fish to a local directory. It's at least private dirty memory in heap |
Description
karl.r.ernst
2011-10-15 17:44:45 UTC
Created attachment 64552 [details]
details of memory usage
I do not want to annoy here ... since it's a pretty old bug report, but I can 100 % reproduce this behaviour with fish:// transfers in Tanglu and Arch Linux. Tell me where to start and I'll do my best to help fixing it. Created attachment 87440 [details]
Showing my memory usage of kio_file during a ssh copy via fish to a local directory.
Screenshot (top) ... and I was wondering why my PC went slower and slower :).
Created attachment 87442 [details]
It's at least private dirty memory in heap
I guess with this we can expect it to be within the kio_file component. The heap memory is actually most of the memory used.
Transferring several 1.2-1.5 gigabyte files here for testing purposes - really 100 % reproducable.
For the record the orignal issue reported here no longer exists because kio_smb (smb://) just like kio_sftp(sftp://) and kio_sftp (ftp://) now implements the "copyToFile" and "copyFromFile" optimizations which do not rely on kio_file when one of the resource a local file. However, since the leakage in kio_file seems to be a real issue and kio_fish, which seems to be no longer maintained, is impacted by it, I will leave this bug report open. Georg, do you see the same problem if you copy from local directory to the ssh server via kio_fish? *** This bug has been marked as a duplicate of bug 339871 *** |