kio_file uses masses of memory after some time running
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dolphin (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
ktorrent (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: ktorrent
After a few hours, ktorrent and it's kio_file slaves use masses of memory. I have Ubuntu 9.10 on an AMD64 system, 4Gb ram. this renders the system extremely slow as almost everything is swapped out. Quitting from ktorrent frees the memory. Simply minimising or leaving it in the system tray does not help. I am sharing two 1.5Gb files.
From top sorting by memory usage:
top - 11:45:58 up 3 days, 13:53, 1 user, load average: 2.39, 1.09, 0.62
Tasks: 176 total, 4 running, 171 sleeping, 0 stopped, 1 zombie
Cpu(s): 3.3%us, 4.0%sy, 0.3%ni, 47.5%id, 44.4%wa, 0.0%hi, 0.5%si, 0.0%st
Mem: 4060760k total, 4030836k used, 29924k free, 312k buffers
Swap: 4104504k total, 2554140k used, 1550364k free, 20120k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
14187 ian 20 0 2501m 1.3g 876 R 0 33.9 23:50.29 kio_file
14188 ian 20 0 2501m 1.3g 876 R 1 33.8 23:59.10 kio_file
And another time:
top - 02:10:27 up 3 days, 8:46, 1 user, load average: 3.26, 3.26, 2.74
Tasks: 175 total, 2 running, 173 sleeping, 0 stopped, 0 zombie
Cpu(s): 1.2%us, 1.0%sy, 0.0%ni, 0.3%id, 97.3%wa, 0.2%hi, 0.0%si, 0.0%st
Mem: 4060760k total, 4032604k used, 28156k free, 304k buffers
Swap: 4104504k total, 2050768k used, 2053736k free, 20012k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
14937 ian 20 0 3576m 3.2g 8 D 0 82.1 34:54.35 kio_file
As you can see, the system is totally bogged down in wait states while it waits for hard drive i/o.
Hi there!
Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https:/ /bugs.kde. org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.
Thanks!