mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Unable to handle transfer rates >2 GiB/s #15871
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#15871
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @HanabishiRecca on GitHub (Jun 27, 2024).
qBittorrent & operating system versions
qBittorrent: 4.6.5
OS: Arch Linux
Qt: 6.7.2
libtorrent: 2.0.10
What is the problem?
I'm actually able to acheive transfers rates more than 2 GiB/s and exceed the max int32 value. This leads to weird results.
Notice the
Unknowncolumn value.And even weirder on a seeding side. Along with
Unknownupload values, I'm actually able to achieve negative share ratio. 🙃There is obvious int wrap around happening here.
The root of the issue actually lies in libtorrent (https://github.com/arvidn/libtorrent/issues/7693).
But qBittorrent itself also has related code parts that should be tweaked. E.g.
github.com/qbittorrent/qBittorrent@610d5ef5ff/src/base/bittorrent/torrentimpl.cpp (L1514-L1524)@xavier2k6 commented on GitHub (Jun 28, 2024):
May be related/relevant.