PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
19785 lvm 20 0 2436m 1.4g 8472 S 24 48.7 440:12.18 deluged
1.1.4 running on 64-bit ubuntu hardy for about two days, seeding about 100 torrents and downloading 1-2 with large number of peers (several thousand). Guys, that's just ridiculous - 1.4G of RAM in two days! 1.1.3 had the same problem, although I never saw anything *that* spectacular. Not sure with which version it started. I've kept memory profiling script running on deluged for the last few days, it started at 130m resident/350m virtual (which is a lot) and grew, sometimes slowly, sometimes quickly, but never shrank. I think we have a major memory leak.
CPU usage also grows until, after several days, deluged starts maxing out a CPU core, at that moment both upload and download speeds start to drop, interface responses become sluggish and deluged has to be restarted. No direct connection with memory usage - in the aforementioned case when deulged gobbled up 1.4G of RAM it was still running smoothly, since then I had to restart it tiwce because of high CPU usage, once after 9 days at 400M and now after just two days at 300M. 1.1.5 ubuntu hardy 64.