https://bugs.kde.org/show_bug.cgi?id=162211
--- Comment #117 from bluescreenaven...@gmail.com --- One odd thing I notice during the test, is that the kioslaves have the high CPU usage, kioclient5 has the high memory usage. I assume that means kioclient5 stores the list of files to copy, and then it must make the kioslave do the copying. My theory was maybe a process (possibly a helper is crashing on the reporters computers, such as kio_file.so) So I tried a smaller, manual test with Dolphin. Copying a smaller directory of ~240000 files, Dolphin's memory usage grows a bit (not a lot). So that confirms my theory that Dolphin must stay alive to tell the kioslaves what file to copy. Killing the kioslave that the CPU usage spiked with did NOT result in a silent failure. I got a dialog warning that the file protocol died, and it gave me some options to recover which it recovered from fully. So it's not silently failing because of that. HOWEVER trying again, I went after Dolphin this time. I closed the Dolphin window. The Dolphin process smartly stayed running to continue the copy (so the issue is not the Dolphin window being clsed). As a test, to simulate a crash or abrupt exit of Dolphin, I killed the Dolphin process. Sure enough the copy stopped. ...and I got a "The copy has completed successfully" notification. I wonder if any of the reports are because of Dolphin going down? -- You are receiving this mail because: You are watching all bug changes.
