Recently, deluge on my lightweight box has been misbehaving. When running, it (python2?) seems to spawn multiple instances even after halting it from the deluge-console or even from a shell via 'killall deluged'. They just keep running rendering the system is incredible unresponsive when this happens. I was able to kill them via 'kill -9 5084 5085 5087' but this isn't normal behavior for deluged.
This box is headless Athlon w/ 512 meg of RAM running Arch Linux (up-to-date) I use for my weather station and for seeding. Looking back at the monitorix logs, it NEVER goes into swap space. Just recently when this has been happening as you can see from the htop screenshot
Glad to post log files and provide more details (currently ~/.config/deluge/deluge.log is a 0-byte file?
I suppose it isn't any leak.
According CPU usage (15%) deluged is doing quite intensive data exchange. It just takes memory for disk cache.
For example, my deluged has disk cache 512Mbytes (32768 16k-pages at tab "cache" of settings).
So, when my deluged is doing its job (seeding/leeching) it can take about 800Mbytes of memory.
for check just delete all torrents from list and take some time to wait
val_dam wrote:I suppose it isn't any leak.
According CPU usage (15%) deluged is doing quite intensive data exchange. It just takes memory for disk cache.
For example, my deluged has disk cache 512Mbytes (32768 16k-pages at tab "cache" of settings).
So, when my deluged is doing its job (seeding/leeching) it can take about 800Mbytes of memory.
for check just delete all torrents from list and take some time to wait
Deluge
