Skip to content
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% of CPU core is used when torrent with mix of I2P and non-I2P trackers is added #7535

Open
Vort opened this issue Oct 23, 2023 · 5 comments

Comments

@Vort
Copy link
Contributor

Vort commented Oct 23, 2023

This problem can be reproduced with I2P mode disabled.
Just run client_test with default parameters, like this: client_test --alert_mask=all and add such magnet link:
magnet:?xt=urn:btih:70260ca39b2867a59f46d81db85eecb256b9365c&dn=I2P%20Update%202.1.0&tr=http%3A%2F%2Ftracker2.postman.i2p%2Fannounce.php&tr=udp%3A%2F%2Ftracker.opentrackr.org%3A1337%2Fannounce
Then observe CPU usage.

I suspect hang may be related to function libtorrent::torrent::update_tracker_timer.

libtorrent version (or branch): 5ce4c51
platform/architecture: Windows x64
compiler and compiler version: clang version 15.0.7

@ukoz
Copy link

ukoz commented Oct 24, 2023

confirm 1 core 100% 2nd 50%, not going past 'no metadata'
209 win64 MSVS 17.7.3

@luzpaz
Copy link
Contributor

luzpaz commented Aug 20, 2024

soft bump

@absolutep
Copy link

Here is the fix - it solved for me atleast in both "mixed mode" as well as "I2P-only mode"

qbittorrent/qBittorrent#21926

@Vort
Copy link
Contributor Author

Vort commented Nov 30, 2024

Here is the fix - it solved for me atleast in both "mixed mode" as well as "I2P-only mode"

This is not a fix, it is avoidance of the problem.

@Neustradamus
Copy link

@arvidn has done a recent PR about I2P:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants