| Summary: | kio_http webdavs eats tons of RAM while copying large files to destination | ||
|---|---|---|---|
| Product: | [Unmaintained] kio | Reporter: | Diego <diego.ml> |
| Component: | webdav | Assignee: | kdelibs bugs <kdelibs-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | adawit |
| Priority: | NOR | ||
| Version: | 4.4 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | HTop showing the huge RAM usage of kio_http webdav | ||
Created attachment 52316 [details] HTop showing the huge RAM usage of kio_http webdav Version: 4.4 (using KDE 4.4.5) OS: Linux I was copying a big file (1.3 GiB) from local filesystem to a local webdavs server through a gigabit connections when it started eating all my RAM. (More than 4GiBs!!) Reproducible: Didn't try Steps to Reproduce: Copy with dolphin a big file from local fs to a webdavs. Actual Results: The transfer occupies all of your RAM rapidly and the system becomes almost unresponsive. Expected Results: Trasfer occupies part of the RAM as buffers, but the system doesn't starts swapping tremendously. Local PC: - encrypted filesystem; - single big file (1.3GiB ISO image); - dual core with 4GiBs RAM and 4GiBs swap. Medium: - gigabit ethernet; Destination server: - alfresco webdavs (webdav through secure connection); - quad core Opteron. I don't think the problem is all the rest: copying the same file to the same server through ssh (fish protocol) occupies the RAM but just as buffer, and does not swap at all.