libtorrent crash (reported) leading to SIGABRT signal crash of qbittorrent #6027

New issue

Closed

opened 2026-02-21 18:11:04 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-21 18:11:04 -05:00

Owner

Originally created by @WaterSibilantFalling on GitHub (Sep 7, 2017).

3.4.0 beta
4.13.0-rc5-686-pae #1 SMP Debian 4.13~~rc5-1~~exp1 (2017-08-14) i686 GNU/Linux
Qt: 5.7.1
libtorrent : 1.1.4

in libtorrent

     < crash >
          :
          :
Catching signal: SIGINT
Exiting cleanly


*************************************************************

then in qbittorrent:

*************************************************************
Catching signal: SIGABRT
Please file a bug report at http://bug.qbittorrent.org and provide the following information:

qBittorrent version: v3.4.0beta
stack trace:
Saving resume data in "/home/me/.local/share/data/qBittorrent/BT_backup/ce281496165bde182de08c0b9e34caa48d95c5fe.fastresume"
  linux-gate.so.1 : __kernel_vsyscall()+0x9  [0xb7f17ce9]
  /lib/i386-linux-gnu/libc.so.6 : gsignal()+0xb0  [0xb6f95dc0]
  /lib/i386-linux-gnu/libc.so.6 : abort()+0x157  [0xb6f97287]
  /usr/lib/i386-linux-gnu/libtorrent-rasterbar.so.9 : assert_fail(char const*, int, char const*, char const*, char const*, int)+0x94  [0xb7a7a1a4]
  /usr/lib/i386-linux-gnu/libtorrent-rasterbar.so.9 : libtorrent::default_storage::write_resume_data(libtorrent::entry&, libtorrent::storage_error&) const+0x160  [0xb7c74280]
  /usr/lib/i386-linux-gnu/libtorrent-rasterbar.so.9 : ()+0xc015c  [0xb7ac515c]
  /usr/lib/i386-linux-gnu/libtorrent-rasterbar.so.9 : ()+0xc0ae9  [0xb7ac5ae9]
  /usr/lib/i386-linux-gnu/libtorrent-rasterbar.so.9 : ()+0xc0f00  [0xb7ac5f00]
  /usr/lib/i386-linux-gnu/libtorrent-rasterbar.so.9 : ()+0xc724d  [0xb7acc24d]
  /usr/lib/i386-linux-gnu/libtorrent-rasterbar.so.9 : ()+0xc8996  [0xb7acd996]
  /usr/lib/i386-linux-gnu/libtorrent-rasterbar.so.9 : ()+0xc84fd  [0xb7acd4fd]
  /lib/i386-linux-gnu/libpthread.so.0 : ()+0x627a  [0xb731727a]
  /lib/i386-linux-gnu/libc.so.6 : clone()+0x66  [0xb7051b56]
Aborted

The libtorrent issue is here: https://github.com/arvidn/libtorrent/issues/2313 with more detail about the libtorrent crash.

Possibly, signals from and death of libtorrent could be caught and qbittorrent could gracefully die, rather than SIGABRT

Originally created by @WaterSibilantFalling on GitHub (Sep 7, 2017). 3.4.0 beta 4.13.0-rc5-686-pae #1 SMP Debian 4.13~rc5-1~exp1 (2017-08-14) i686 GNU/Linux Qt: 5.7.1 libtorrent : 1.1.4 in libtorrent ``` < crash > : : Catching signal: SIGINT Exiting cleanly ************************************************************* ``` then in qbittorrent: ``` ************************************************************* Catching signal: SIGABRT Please file a bug report at http://bug.qbittorrent.org and provide the following information: qBittorrent version: v3.4.0beta stack trace: Saving resume data in "/home/me/.local/share/data/qBittorrent/BT_backup/ce281496165bde182de08c0b9e34caa48d95c5fe.fastresume" linux-gate.so.1 : __kernel_vsyscall()+0x9 [0xb7f17ce9] /lib/i386-linux-gnu/libc.so.6 : gsignal()+0xb0 [0xb6f95dc0] /lib/i386-linux-gnu/libc.so.6 : abort()+0x157 [0xb6f97287] /usr/lib/i386-linux-gnu/libtorrent-rasterbar.so.9 : assert_fail(char const*, int, char const*, char const*, char const*, int)+0x94 [0xb7a7a1a4] /usr/lib/i386-linux-gnu/libtorrent-rasterbar.so.9 : libtorrent::default_storage::write_resume_data(libtorrent::entry&, libtorrent::storage_error&) const+0x160 [0xb7c74280] /usr/lib/i386-linux-gnu/libtorrent-rasterbar.so.9 : ()+0xc015c [0xb7ac515c] /usr/lib/i386-linux-gnu/libtorrent-rasterbar.so.9 : ()+0xc0ae9 [0xb7ac5ae9] /usr/lib/i386-linux-gnu/libtorrent-rasterbar.so.9 : ()+0xc0f00 [0xb7ac5f00] /usr/lib/i386-linux-gnu/libtorrent-rasterbar.so.9 : ()+0xc724d [0xb7acc24d] /usr/lib/i386-linux-gnu/libtorrent-rasterbar.so.9 : ()+0xc8996 [0xb7acd996] /usr/lib/i386-linux-gnu/libtorrent-rasterbar.so.9 : ()+0xc84fd [0xb7acd4fd] /lib/i386-linux-gnu/libpthread.so.0 : ()+0x627a [0xb731727a] /lib/i386-linux-gnu/libc.so.6 : clone()+0x66 [0xb7051b56] Aborted ``` The libtorrent issue is here: https://github.com/arvidn/libtorrent/issues/2313 with more detail about the libtorrent crash. Possibly, signals from and death of libtorrent could be caught and qbittorrent could gracefully die, rather than SIGABRT

deekerman

2026-02-21 18:11:04 -05:00

closed this issue
added the
Crash
label

deekerman commented

2026-02-21 18:11:10 -05:00

Author

Owner

@ngosang commented on GitHub (Sep 16, 2018):

We are closing all issues related to old qBittorrent versions (qBittorrent < 4.1.0).
Please, update to last release and, if the bug/error/crash is still present, open another issue.
Thank you.

@ngosang commented on GitHub (Sep 16, 2018): We are closing all issues related to old qBittorrent versions (qBittorrent < 4.1.0). Please, update to last release and, if the bug/error/crash is still present, open another issue. Thank you.