Deluge
This is on deluge 1.3.5 as well as earlier (1.3.4) . I have seen this peculiar habit when deluge is on multi-file torrents specifically large torrents (say 10 GB or more) where each file is around 300-400 MB and the number of files are around +30 or something. The piece size is say 2 MB or more . Now what I usually do in such torrents is that I attempt to download a single file at the time in order to save space. Now it's at the very last 3-4 pieces that I get into trouble and it takes a very long long time if they actually complete.
I do see this in the changelog but dunno if it means anything.
Looking forward to know if something can be done.Fix not properly detecting when torrent is at end of queue
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages deluge depends on:
ii deluge-gtk 1.3.4-1
ii python 2.7.2-10
ii python-libtorrent 0.15.10-1+b1
deluge recommends no packages.
deluge suggests no packages.
-- no debconf information
