Torrent queueing- min threshold not honored for "Max Active Torrents" #8458

New issue

Open

opened 2026-02-21 19:37:35 -05:00 by deekerman · 0 comments

deekerman commented

2026-02-21 19:37:35 -05:00

Owner

Originally created by @beerandt on GitHub (Mar 13, 2019).

Please provide the following information

qBittorrent version and Operating System

4.1.5 windows 7 x64

If on linux, libtorrent and Qt version

(type here)

What is the problem

Torrents in excess of #set as "Maximum Active Torrents" (under torrent queueing) are queued, even if below minimum thresholds ("Do not count slow torrents..."

Settings for max active up and max active down seem to work as expected.

What is the expected behavior

Active torrents that do not meet the min thresholds should not be counted as active for the purpose of queueing.

Steps to reproduce

Set maximum active torrents setting at a value that exceeds actually active torrents. Set minimum threshold high enough that most/all torrents should not be counted as active for purposes of queueing.

Observe number of queued (status) torrents: equals # of resumed torrents - setting of maximum active torrents. Ie- behavior of maximum active torrents is not modified by the "Do not count slow torrents..." checkbox.

Extra info(if any)

In my case, this was first observed when exceeding 999 active torrents, which is the maximum value allowed in the setting. Allowing a value greater than 999 (or 0 for unlimited) would also be a helpful workaround. (Unless there is a reason I'm unaware of for a hard limit of 999.)

I am unable to test at a lower number until I have time to clone the machine to a VM.

Originally created by @beerandt on GitHub (Mar 13, 2019). **Please provide the following information** ### qBittorrent version and Operating System 4.1.5 windows 7 x64 ### If on linux, libtorrent and Qt version (type here) ### What is the problem Torrents in excess of #set as "Maximum Active Torrents" (under torrent queueing) are queued, even if below minimum thresholds ("Do not count slow torrents..." Settings for max active up and max active down seem to work as expected. ### What is the expected behavior Active torrents that do not meet the min thresholds should not be counted as active for the purpose of queueing. ### Steps to reproduce Set maximum active torrents setting at a value that exceeds actually active torrents. Set minimum threshold high enough that most/all torrents should not be counted as active for purposes of queueing. Observe number of queued (status) torrents: equals # of resumed torrents - setting of maximum active torrents. Ie- behavior of maximum active torrents is not modified by the "Do not count slow torrents..." checkbox. ### Extra info(if any) In my case, this was first observed when exceeding 999 active torrents, which is the maximum value allowed in the setting. Allowing a value greater than 999 (or 0 for unlimited) would also be a helpful workaround. (Unless there is a reason I'm unaware of for a hard limit of 999.) I am unable to test at a lower number until I have time to clone the machine to a VM.