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

Ncurses interface hangs for a really long time, can't interact or exit rTorrent #1363

Closed
8dcc opened this issue Jan 3, 2025 · 4 comments
Closed

Comments

@8dcc
Copy link

8dcc commented Jan 3, 2025

I built rtorrent 0.9.8 with the --with-xmlrpc-c=yes flag (although this issue happens even if I omit the option), along with libtorrent 0.13.8.

As soon as I add torrents, the program hangs for very large periods of time, depending on the torrent amount. Right now I have around 40 and it takes many minutes to respond to my keys, but the issue happens with 5 torrents, or even 1 (on a smaller scale). At first, I was adding torrents with magnet links, but I also tried adding .torrent files and it also happens.

This issue happens in two different machines, one uses Arch (kernel 6.12.7) and the other Guix (kernel 6.11.11). My current configuration (at the time of writing issue) can be found here.

I am not sure how I would debug/profile this program but, if you need me to, I will try.

@stickz
Copy link
Contributor

stickz commented Jan 3, 2025

Could you upgrade to the latest version of rTorrent? We can't investigate your problem, unless you use our latest changes.

@8dcc
Copy link
Author

8dcc commented Jan 4, 2025

My issue is probably related to #180 and perhaps #234.

@stickz
Copy link
Contributor

stickz commented Jan 4, 2025

My issue is probably related to #180 and perhaps #234.

trackers.delay_scrape = yes was added in v0.10.0. Have you tried that new feature? It addresses #180. There were also multiple other performance and stability patches leading up to v0.15.1. The latest version should be fine with only 40 torrents.

@8dcc
Copy link
Author

8dcc commented Jan 7, 2025

It seems the issue was the DNS. Some program was overwriting /etc/resolv.conf and I was using my ISP's DNS, which (I assume) blocks a lot of tracker's domains. Modifying this file fixed the issue on both machines.

@8dcc 8dcc closed this as completed Jan 7, 2025
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

2 participants