-
-
Notifications
You must be signed in to change notification settings - Fork 209
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
Regular rtorrent crashes because of DHT #209
Comments
I've got that backtrace, plus this one which appears to be a double-free:
#166 has this valgrind output from a couple years ago: https://gist.github.com/slingamn/578793a4b7eeffd0a564daa707a2ac1b |
jesec
added a commit
to jesec/libtorrent
that referenced
this issue
May 23, 2022
Use-after-free occurs when the transaction ID is exhausted. As the ID only has one char, on an instance with many torrents, it is easy to exhaust the ID space, so that new transactions have to be discarded. However, The new transaction could be associated with an ongoing DhtSearch that does not expect transaction to be freed. Follow up of "dht_server: fix potential use-after-free" (1418bf9), properly fix the issue and deal with memory leak with this method. Bug: rakshasa/libtorrent#166, rakshasa/libtorrent#209, rakshasa/libtorrent#944
Any chance for fixing this? DHT is very very needed thing in rtorrent, it's a shame such a good client crashes. Lot of serious pro seeders rely on it. I even want to pay to whoever fixes and pushes the changes. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After many crashes, I found another issue where gdb was mentioned and did the same to provide a better stack trace:
Disabling DHT fixed the crashes, but I'd like to use it again. I compiled xmlrpc-c (advanced, v1.57.0), libtorrent (v0.13.8) and rtorrent (v0.9.8) like it's described here, except that I had to run
export PKG_CONFIG_PATH=/usr/local/lib64/pkgconfig
before calling./configure
.Any guess what could be the problem or a hint what I could do to provide more information?
The text was updated successfully, but these errors were encountered: