Rtorrent: Rtorrent crashing with segmentation fault every 30 seconds

[dirtycajunrice]

Logging set for debug:

# Log info
log.open_file = "rtorrent.log", (cat,/config/log/rtorrent/rtorrent.log.,(system.pid))
log.open_file = "torrent.log", (cat,/config/log/rtorrent/torrent.log.,(system.pid))
log.open_file = "tracker.log", (cat,/config/log/rtorrent/tracker.log.,(system.pid))
log.open_file = "thread.log", (cat,/config/log/rtorrent/thread.log.,(system.pid))
log.open_file = "peer.log", (cat,/config/log/rtorrent/peer.log.,(system.pid))
log.open_file = "socket.log", (cat,/config/log/rtorrent/socket.log.,(system.pid))
log.open_file = "storage.log", (cat,/config/log/rtorrent/storage.log.,(system.pid))

log.add_output = "debug", "rtorrent.log"
log.add_output = "torrent_debug", "torrent.log"
log.add_output = "tracker_debug", "tracker.log"
log.add_output = "thread_debug", "thread.log"
log.add_output = "peer_debug", "peer.log"
log.add_output = "socket_debug", "socket.log"
log.add_output = "storage_debug", "storage.log"

torrents: ~3300

Error:

1557162266 C Caught signal: 'Segmentation fault.
---DUMP---
Caught Segmentation fault, dumping stack:
Stack dump not enabled.

---END---

Cant see anything specific causing it... any help would be appreciated. This is running in a linuxserver/rutorrent container that was fine until recently.

error with the binhex container that has stack dump:

Caught Segmentation fault, dumping stack:
/usr/bin/rtorrent(+0x3e77e) [0x5567a342177e]
/usr/lib/libc.so.6(+0x37e00) [0x7fca7eebbe00]
/usr/lib/libcurl.so.4(+0x3675b) [0x7fca7f3a475b]
/usr/lib/libcurl.so.4(curl_multi_socket_action+0x25) [0x7fca7f3a4b25]
/usr/bin/rtorrent(+0x13f9cb) [0x5567a35229cb]
/usr/lib/libtorrent.so.19(_ZN7torrent9PollEPoll7performEv+0xca) [0x7fca7f2941ba]
/usr/lib/libtorrent.so.19(_ZN7torrent9PollEPoll7do_pollEli+0x71) [0x7fca7f2943f1]
/usr/lib/libtorrent.so.19(_ZN7torrent11thread_base10event_loopEPS0_+0x118) [0x7fca7f2c9768]
/usr/bin/rtorrent(+0x3d80c) [0x5567a342080c]
/usr/lib/libc.so.6(__libc_start_main+0xf3) [0x7fca7eea8223]
/usr/bin/rtorrent(+0x3e04e) [0x5567a342104e]

---END---

[kannibalox]

Is there anything interesting in the log files? Generally this is the result of a single torrent where the underlying storage is having issues, you can try narrowing it down by backing up the session directory, clearing it out, and adding session file triples back in until you find the file that's causing the response.

[dirtycajunrice]

i ended up sticking with the binhex container and reverting curl back to
the 7.63 version and its fine. reverting to 7.63 didnt fix the alpine based
linuxserver/rutorrent container though (as a note). so as other issues have
pointed out 7.64.x curl has some issues in some capacity

[Markismus]

This looks rather a lot like mine:

Caught Segmentation fault, dumping stack:
/usr/bin/rtorrent(+0x465a0) [0x55f82d2ae5a0]
/usr/lib/libc.so.6(+0x3a7e0) [0x7f40ec3767e0]
/usr/lib/libtorrent.so.19(_ZN7torrent9PollEPoll11insert_readEPNS_5EventE+0x74) [0x7f40ec7b03b4]
/usr/bin/rtorrent(+0x150e6b) [0x55f82d3b8e6b]
/usr/lib/libcurl.so.4(+0x32fbc) [0x7f40ec8b1fbc]
/usr/lib/libcurl.so.4(+0x3615f) [0x7f40ec8b515f]
/usr/lib/libcurl.so.4(curl_multi_socket_action+0x25) [0x7f40ec8b5315]
/usr/bin/rtorrent(+0x14ef12) [0x55f82d3b6f12]
/usr/bin/rtorrent(+0x14efe4) [0x55f82d3b6fe4]
/usr/bin/rtorrent(+0x4741d) [0x55f82d2af41d]
/usr/lib/libtorrent.so.19(_ZN7torrent11thread_base10event_loopEPS0_+0x15d) [0x7f40ec7e150d]
/usr/bin/rtorrent(+0x453ec) [0x55f82d2ad3ec]
/usr/lib/libc.so.6(__libc_start_main+0xf3) [0x7f40ec362ee3]
/usr/bin/rtorrent(+0x45c2e) [0x55f82d2adc2e]

---END---

Reverted to curl-7.62.0-1 from 7.65.1-2 and the problem is gone.

[rsvensson]

Can confirm that it seems to be an issue with curl 7.65.1. I downgraded to 7.64.1 and retried and now it works as expected again.

I'm on Arch Linux.

[rakshasa]

Duplicate, that curl version is buggy.

[mvegetto]

I can also confirm that it seems to be an issue with curl 7.65.1. I have downgraded to 7.64.0-4 and no more issues.