Deluge
Memory leak in 1.3
Re: Memory leak in 1.3
Ok, I have this issue too! Running Deluge 1.3.3 and libtorrent-rasterbar 0.15.7. deluged takes up all available memory.
Re: Memory leak in 1.3
So, after more investigation, it seems to be due to a tracker which is down.. Getting a connection refused error with it.. And memory usage is increasing 
Re: Memory leak in 1.3
The last post here by flasher360 explains what to do then, also you have failed to mention what OS you are using.kalpik wrote:Ok, I have this issue too! Running Deluge 1.3.3 and libtorrent-rasterbar 0.15.7. deluged takes up all available memory.
flasher360 wrote:then please post your system-settings and deluge/libtorrent versions in the ticket mentioned above.
thanks.
Re: Memory leak in 1.3
Oops! On Archlinux.
Re: Memory leak in 1.3
Oh, and tried to add comment to bug tracker, but getting:
No permission to change ticket fields.
No permissions to add a comment.
EDIT: Scratch that! Had to verify my email
No permission to change ticket fields.
No permissions to add a comment.
EDIT: Scratch that! Had to verify my email
Re: Memory leak in 1.3
Oh man, was searching for a decent alternative to Deluge, and there isn't any! Deluge is THAT good! Oh how I wish this memory leak is fixed soon! 
Re: Memory leak in 1.3
I can attest to this problem.
Started happening today when I did an apt-get on my debian/testing server.
The things that changed were
1. The linux-kernel. Went from the latest 2.6 kernel --> 3.0.0+99
2. Libtorrent
Used memory keeps growing until all virtual memory is used at which point the OS crashes or until I stop deluge-daemon.
It seems no cached memory is freed.
Started happening today when I did an apt-get on my debian/testing server.
The things that changed were
1. The linux-kernel. Went from the latest 2.6 kernel --> 3.0.0+99
2. Libtorrent
Used memory keeps growing until all virtual memory is used at which point the OS crashes or until I stop deluge-daemon.
It seems no cached memory is freed.