We have an issue randomly happening (seems to hit every 24-48 hours, and not on every torrent). A match happens and the .torrent download is initiated but then hangs.
The first log shows the match and initiating the download (read/writing on socket 6).
After this it just hangs indefinitely, the irssi UI is completely locked and needs to be forcefully killed and restarted.
I haven't had a chance to look at the functions involved yet, but it looks like it could be an error/unexpected response from the http server of the tracker when downloading the .torrent which isn't being properly timed out/error thrown.
We have an issue randomly happening (seems to hit every 24-48 hours, and not on every torrent). A match happens and the .torrent download is initiated but then hangs.
The first log shows the match and initiating the download (read/writing on socket 6).
It shows Resource temporarily unavailable (waiting for read) until the below response is received.
After this it just hangs indefinitely, the irssi UI is completely locked and needs to be forcefully killed and restarted.
I haven't had a chance to look at the functions involved yet, but it looks like it could be an error/unexpected response from the http server of the tracker when downloading the .torrent which isn't being properly timed out/error thrown.