teh_g wrote:I am seeing the memory and CPU issue as well on Debian 5.

then please post your system-settings and deluge/libtorrent versions in the ticket mentioned above.
thanks.

new ticket for memory leak: http://dev.deluge-torrent.org/ticket/1454

older ticket for "open folder" cpu problem: http://dev.deluge-torrent.org/ticket/1396

launched it non-classic. after some hours running: deluged still consumes about 2,2% memory /usr/bin/deluge goes up from 1,7% to somewhere ridiculous. (the longer it's running the more memory it consumes) so it seems that the deluge gtk/ui is causing the problems. what to do next? i found the ticket...

seems to be a different problem but i don't want to leave it unmentioned:
when i rightclick a torrent and choose "open folder" the folder opens up
but deluge goes up to 100% cpu-usage and remains there until i kill it?!

cache-size: 512 (16 KiB blocks)
cache lifetime: 60 (seconds)

hi,
i did another test:
i started deluge and paused all torrents.
30 minutes long - no additional memory was used.
as soon as i start the torrents the memory usage goes up.

if you still want me to launch it "non classic" then i will do. should i?

still leakin'
which logs should i provide?
in my opinion "deluge -L debug" doesn't contain any important information.

*bump*

fukt wrote:I found out that I don't have to restart Deluge to free up the memory. Just select all torrents, press pause and then resume also works.

FYI: doesn't work for me. i have to restart deluge to free up memory.

in my case the only plugin activated is banlist.

which logs do you mean?
the logs when deluge is started with "-L debug"?
i'll give you any log you want ;D