From activity system detail: "It is using 3.2 GB privately, and a further 19.9 MB that is, or could be, shared with other programs. Dividing up the shared memory between all the processes sharing that memory we get a reduced shared memory usage of 1439.0 KB. Adding that to the private usage, we get the above mentioned total memory footprint of 3.2 GB." :~$ top -d 12 top - 11:30:20 up 18:48, 3 users, load average: 0,78, 0,97, 1,12 Tasks: 254 total, 5 running, 249 sleeping, 0 stopped, 0 zombie %Cpu(s): 11,9 us, 6,8 sy, 1,4 ni, 79,4 id, 0,3 wa, 0,0 hi, 0,2 si, 0,0 st KiB Mem: 8119100 total, 7994144 used, 124956 free, 16292 buffers KiB Swap: 0 total, 0 used, 0 free. 1392064 cached Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 25477 guillau+ 20 0 4220264 3,549g 3248 R 7,8 45,8 25:50.39 kio_file Reproducible: Couldn't Reproduce
Created attachment 89089 [details] screen of activity system
I have forgotten to say that I'm copying files via ssh. Another link: https://bugs.launchpad.net/ubuntu/+source/ktorrent/+bug/503841
After 2 hours, the used ram is 4.2 Go: :~$ top -d 12 top - 12:28:24 up 19:46, 3 users, load average: 1,23, 0,93, 0,92 Tasks: 250 total, 4 running, 246 sleeping, 0 stopped, 0 zombie %Cpu(s): 13,7 us, 8,6 sy, 0,1 ni, 77,2 id, 0,2 wa, 0,0 hi, 0,2 si, 0,0 st KiB Mem: 8119100 total, 7967528 used, 151572 free, 2364 buffers KiB Swap: 0 total, 0 used, 0 free. 856652 cached Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 25477 guillau+ 20 0 4889544 4,214g 3132 S 9,3 54,4 31:13.96 kio_file
> copying files via ssh Are you copying from local to ssh or from ssh to local? There seems to be a leak inside kio_file when copying, but to get to gigabytes memory leak you were probably copying terabytes?
I'm copying files from ssh to local, about 500Go (200 files) The source is a Raspberry Pi's hard drive connected with USB, and the destination is an external drive connected in eSATA to the local KDE machine. (I can't remove the first hd of the rpi, it should be more easy !!) So, after the ram was completly full (and the machine started to freeze), I had to stop the copy and re-launch it with the non-copied files. I have looked the process evolution, and it seems that the process take 1Mb every 5s, something like that. (In reply to Christoph Feck from comment #4) > > copying files via ssh > > Are you copying from local to ssh or from ssh to local? There seems to be a > leak inside kio_file when copying, but to get to gigabytes memory leak you > were probably copying terabytes?
(All HDs file-system is ext4)
Copying from ssh to local should not involve kio_file if you are using the kio_sftp (sftp://). Such copy should involve only kio_sftp. So are you using kio_fish (fish://) to copy these files?
> So are you using kio_fish (fish://) to copy these files? Yes, I have configured Dolphin with fish://pi@192.168.2.2:22/home/pi/ and I copy the files with it. Sorry for the confuse.
Dawit, does comment #8 provide the requested information? Please set the bug status or add a comment.
Yes. This seems to be a kio_file issue to me. I could not find the source of the leak even though I attempted to debug kio_file using valgrind.
*** Bug 342145 has been marked as a duplicate of this bug. ***
*** Bug 284117 has been marked as a duplicate of this bug. ***
I've never seen this happen with a KF5 version of KIO. Is this still an issue for anyone with KDE Frameworks 5.47 and Dolphin 18.04.x?
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 set the bug status 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 is solved in the 18.04 version (Kubuntu x64) Thanks
Thanks for confirming!