doesn't seed without limits (since 3.3.0) #3860

New issue

Closed

opened 2026-02-21 17:00:06 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-21 17:00:06 -05:00

Owner

Originally created by @SEVENID on GitHub (Jan 29, 2016).

When connection limits (global and per torrent) are unchecked (what, as i understand, means unlimited) real seeding speed approach zero - about 100 KBps, but when values more then 100 gives real - more then 2 MBps.

Sorry for my English, but it seems really strange.

Thanks.

Originally created by @SEVENID on GitHub (Jan 29, 2016). When connection limits (global and per torrent) are unchecked (what, as i understand, means unlimited) real seeding speed approach zero - about 100 KBps, but when values more then 100 gives real - more then 2 MBps. Sorry for my English, but it seems really strange. Thanks.

deekerman

2026-02-21 17:00:06 -05:00

closed this issue
added the
autoCloseOldIssue
label

deekerman commented

2026-02-21 17:00:12 -05:00

Author

Owner

@PadaV4 commented on GitHub (Feb 9, 2016):

Sounds similar to the issue i posted a while ago!! Unfortunately nobody did look into it.. #4617

@PadaV4 commented on GitHub (Feb 9, 2016): Sounds similar to the issue i posted a while ago!! Unfortunately nobody did look into it.. #4617

deekerman commented

2026-02-21 17:00:12 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Oct 29, 2020):

This issue has been closed and locked for being too old, and thus either most likely resolved in recent versions or no longer applicable.
If you experience the reported problem or similar in the latest version, please open a new issue report with the requested information in the issue template.

A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression.
Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar.
Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression.

Thank you for your contributions.

@sledgehammer999 commented on GitHub (Oct 29, 2020): This issue has been closed and locked for being too old, and thus either most likely resolved in recent versions or no longer applicable. If you experience the reported problem or similar in the **latest** version, please open a new issue report with the requested information in the issue template. A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression. Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar. Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression. Thank you for your contributions.