yes, and we do. the thing is, we only wait 5 seconds for the tracker to respond when exiting. if it doesnt respond within that time, we close and they dont get the full stop message. it's a tricky subject. if we increase the limit, then you wont be able to restart deluge right away after closing, p...

Excellent idea, I'll be happy to offer some of my bandwidth for this. However, the above download links require a lot of clicking (and I'm lazy by nature :) ). Any chance of getting a list of direct download locations for the torrents, that we could just feed to wget? *edit* in fact, when I click an...

markybob wrote: yep, it's fixed

Awesome, I like it when problems get fixed before I even notice they existed

I can't confirm a re-occurance of the memory leak this time. I just updated to 2263, it's currently seeding two rather big torrents (40GiB and 60GiB) and downloading another 6GiB. Over the hour it's been running now, memory usage has crept up from 3.1% to 4.1%, so that's nowhere near the scale of us...

"forced seed" would be the same thing as having the ratio not set Based on my observations, it seems you're talking about the global ratio setting (Preferences/Seeding/Stop Seeding...) This appears to work as expected, option enabled (checked): deluge stops seeding when the desired ratio ...

Azureus has a 'Force Start' option, which essentially ignores the set ignore ratio. I just checked out the 'Desired Ratio' plugin, but that appears far too limited (choices of 1, 2, 3, or default). I'd love to see either a force seed option or an option to manually set the desired ratio to arbitrary...

Looks like 2205 fixes it, thanks loads :) It's been running for about 45 minutes now and memory sits tightly just over 90MiB. Unfortunately, I'm not a very experienced programmer, I took a brief look at the diffs between 2204 and 2205, but can't make heads or tails from it. If anyone does make a cha...

I experienced similar high memory usage yesterday, running revision 2195. I don't have any plugins enabled, running on Ubuntu 7.10 (32-bit). I'll update to 2204 and update this post with results. *Update* I updated to 2204, the memory leak still seems to be there. I did some more testing, deluge run...