qBittorrent has crashed #12619

New issue

Closed

opened 2026-02-21 22:57:43 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-21 22:57:43 -05:00

Owner

Originally created by @shellyofthemud on GitHub (Nov 27, 2021).

qBittorrent & operating system versions

qBittorrent-nox: v4.1.5 x64
Operating system: debian 4.19.208-1
Qt: none
libtorrent-rasterbar: 1.1.11

What is the problem?

Caught signal: SIGSEGV
Stack trace:
/lib/x86_64-linux-gnu/libQt5Network.so.5 : ()+0x95b84 [0x7f79e6a7bb84]
/lib/x86_64-linux-gnu/libQt5Network.so.5 : ()+0x94c49 [0x7f79e6a7ac49]
/lib/x86_64-linux-gnu/libQt5Core.so.5 : QObject::event(QEvent*)+0xe2 [0x7f79e6740072]
/lib/x86_64-linux-gnu/libQt5Core.so.5 : QCoreApplication::notifyInternal2(QObject*, QEvent*)+0x156 [0x7f79e6716466]
/lib/x86_64-linux-gnu/libQt5Core.so.5 : QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*)+0x1cb [0x7f79e671946b]
/lib/x86_64-linux-gnu/libQt5Core.so.5 : ()+0x2bc103 [0x7f79e6768103]
/lib/x86_64-linux-gnu/libglib-2.0.so.0 : g_main_context_dispatch()+0x2ae [0x7f79e55f5fee]
/lib/x86_64-linux-gnu/libglib-2.0.so.0 : ()+0x4e288 [0x7f79e55f6288]
/lib/x86_64-linux-gnu/libglib-2.0.so.0 : g_main_context_iteration()+0x2c [0x7f79e55f631c]
/lib/x86_64-linux-gnu/libQt5Core.so.5 : QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag)+0x67 [0x7f79e6767727]
/lib/x86_64-linux-gnu/libQt5Core.so.5 : QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag)+0x13b [0x7f79e671515b]
/lib/x86_64-linux-gnu/libQt5Core.so.5 : QThread::exec()+0xb6 [0x7f79e6564e76]
/lib/x86_64-linux-gnu/libQt5Core.so.5 : ()+0xc2a67 [0x7f79e656ea67]
/lib/x86_64-linux-gnu/libpthread.so.0 : ()+0x7fa3 [0x7f79e6490fa3]
/lib/x86_64-linux-gnu/libc.so.6 : clone()+0x3f [0x7f79e60a04cf]
Segmentation fault

Steps to reproduce

Start qbittorent-nox -d
log in to web console
wait for crash

Additional context

There are no torrents currently active or stored. The file destination is set to a mounted NFS share. logging into the web ui isn't even necessary, I simply start qbittorrent-nox and it fails after 30 seconds or so.

Log(s) & preferences file(s)

No response

Originally created by @shellyofthemud on GitHub (Nov 27, 2021). ### qBittorrent & operating system versions qBittorrent-nox: v4.1.5 x64 Operating system: debian 4.19.208-1 Qt: none libtorrent-rasterbar: 1.1.11 ### What is the problem? Caught signal: SIGSEGV Stack trace: /lib/x86_64-linux-gnu/libQt5Network.so.5 : ()+0x95b84 [0x7f79e6a7bb84] /lib/x86_64-linux-gnu/libQt5Network.so.5 : ()+0x94c49 [0x7f79e6a7ac49] /lib/x86_64-linux-gnu/libQt5Core.so.5 : QObject::event(QEvent*)+0xe2 [0x7f79e6740072] /lib/x86_64-linux-gnu/libQt5Core.so.5 : QCoreApplication::notifyInternal2(QObject*, QEvent*)+0x156 [0x7f79e6716466] /lib/x86_64-linux-gnu/libQt5Core.so.5 : QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*)+0x1cb [0x7f79e671946b] /lib/x86_64-linux-gnu/libQt5Core.so.5 : ()+0x2bc103 [0x7f79e6768103] /lib/x86_64-linux-gnu/libglib-2.0.so.0 : g_main_context_dispatch()+0x2ae [0x7f79e55f5fee] /lib/x86_64-linux-gnu/libglib-2.0.so.0 : ()+0x4e288 [0x7f79e55f6288] /lib/x86_64-linux-gnu/libglib-2.0.so.0 : g_main_context_iteration()+0x2c [0x7f79e55f631c] /lib/x86_64-linux-gnu/libQt5Core.so.5 : QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)+0x67 [0x7f79e6767727] /lib/x86_64-linux-gnu/libQt5Core.so.5 : QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>)+0x13b [0x7f79e671515b] /lib/x86_64-linux-gnu/libQt5Core.so.5 : QThread::exec()+0xb6 [0x7f79e6564e76] /lib/x86_64-linux-gnu/libQt5Core.so.5 : ()+0xc2a67 [0x7f79e656ea67] /lib/x86_64-linux-gnu/libpthread.so.0 : ()+0x7fa3 [0x7f79e6490fa3] /lib/x86_64-linux-gnu/libc.so.6 : clone()+0x3f [0x7f79e60a04cf] Segmentation fault ### Steps to reproduce 1. Start qbittorent-nox -d 2. log in to web console 3. wait for crash ### Additional context There are no torrents currently active or stored. The file destination is set to a mounted NFS share. logging into the web ui isn't even necessary, I simply start qbittorrent-nox and it fails after 30 seconds or so. ### Log(s) & preferences file(s) _No response_