Opened 11 years ago
Last modified 10 years ago
#2331 new bug
"Total active" torrents limit in prefs does not ignore slow or inactive torrents with "Do not count slow torrents" checked
Reported by: | justaluser | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | not applicable |
Component: | libtorrent | Version: | 1.3.6 |
Keywords: | Cc: |
Description
"Total active" torrents limit in prefs does not ignore slow or inactive torrents with "Do not count slow torrents" checked.
It seems that the individual "Total active downloading" and "Total active seeding" limits obey the "Do not count slow" box, but the total limit does not, which severely limits the functionality of this feature. For instance, if I wish to have a large number of fairly inactive torrents seeding "inactively" until a leech needs them, I have to raise the "Total active" limit to a number larger than the total number of torrents I have. For now, I have set that number high (after scratching my head for quite a while until I tried that), but it was very nearly a deal-breaker for me, as my previous BT client can seed dozens of inactive torrents by default.
Not sure which component this falls under.
Using a source-built 1.3.6 GTK-UI on Debian 7.0 Wheezy (bug was also present in the standard Wheezy package of 1.3.3), libtorrent version 0.15.10-1+b1 (stock version in the Wheezy repos). I'm curious to try using a newer libtorrent, but there's no package available and building it seems to be a particularly painful process.
Change History (2)
comment:1 by , 10 years ago
Component: | other/unknown → libtorrent |
---|---|
Milestone: | Future → not applicable |
comment:2 by , 10 years ago
Libtorrent fixed this in commit r9968.
You can find it in 1.0.0+, but not in 0.16.x branch as of this comment (0.16.19).
Unfortunately, the deluge PPAs do not ship with libtorrent 1.0.x yet but you can try and compile libtorrent yourself.
This will be an issue in libtorrent which potentially is fixed in later versions e.g. 0.16 or 1.0, if you find it is not then it will require reporting to the libtorrent bugtracker.