-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
100% CPU use with many torrents announcing to a tracker with an expired certificate #15623
Comments
Nice find! you should also report this problem upstream: https://github.com/arvidn/libtorrent/issues |
I could not reproduce it. I tested with 1000 torrents with 7-8 trackers that had expired certificates. |
there was an issue related to HTTP tracker DNS lookups that, if they took too long, could trigger a 100% CPU busy loop. It was fixed in the recently released libtorrent 1.2.17 and 2.0.7 |
I’m not sure if they’re the same issue but this ticket indicates that turning off https tracker validation fixed it for OP. |
qBittorrent & operating system versions
qBittorrent: 4.3.8 x64
Operating system: NixOS 21.11-pre, NixOS 21.05
Qt: 5.15.2
libtorrent-rasterbar: 2.0.3, 2.0.4, or arvidn/libtorrent@69cb589
Specifically, I confirmed this issue and saw the same behavior with:
What is the problem?
qBittorrent/libtorrent seems to use 100% CPU (one core) when it has many torrents announcing to a tracker with an expired HTTPS certificate.
There isn't really any visible indication or logging that indicates the problem, I just lucked into figuring it out.
Steps to reproduce
strace
showing one of the qbittorrent threads spinning fast onepoll_wait(15, [], 128, 0) = 0
Additional context
with 'Validate HTTP tracker certificates':
without 'Validate HTTP tracker certificates':
Log(s) & preferences file(s)
No response
The text was updated successfully, but these errors were encountered: