mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Crash after adding torrent, after that qbittorrent keeps crashing at startup, dependably each time. #9729
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#9729
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @vlijmenfileer on GitHub (Feb 5, 2020).
qBittorrent version and Operating System
qt5ct: using qt5ct plugin
qBittorrent v4.1.5
OS: Debian GNU/Linux 10 (buster) x86_64
Model: Dell System XPS L502X
Kernel: 5.2.0-0.bpo.3-amd64
Resolution: 1920x1080
DE: Xfce
WM: Xfwm4
WM Theme: Breeze
Theme: Clearlooks-Phenix [GTK2], Breeze [GTK3]
Icons: Tango [GTK2], breeze [GTK3]
Terminal: xfce4-terminal
Terminal Font: Monospace 11
CPU: Intel i5-2520M (4) @ 3.200GHz
GPU: NVIDIA GeForce GT 525M
GPU: Intel 2nd Generation Core Processor Family
Memory: 5429MiB / 7935MiB
If on linux, libtorrent-rasterbar and Qt version
libtorrent-rasterbar: v9, 1.1.11
qt: 5.11.3
What is the problem
Crash after adding torrent, after that qbittorrent keeps crashing at startup, dependably each time.
This happened too the other day, in that instance it kept running long enough before crashing for me to pick up something specific to one torrent (forgot what) that made me delete that specific torrent.
This time, the crash after start happens too quick to be able to find out anything, rendering qbittorrent dysfunctional.
What is the expected behavior
No crash
Steps to reproduce
(type here)
Extra info(if any)
Output of qbittorrent when started from a shell:
qt5ct: using qt5ct plugin
qt5ct: D-Bus global menu: no
qt5ct: D-Bus system tray: no
qt5ct: custom style sheet is disabled
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
DSvgRenderer::load: Error domain 1 code 76 on line 1 column 168 of data: Opening and ending tag mismatch: meta line 0 and head
Please file a bug report at http://bug.qbittorrent.org and provide the following information:
qBittorrent version: v4.1.5
Caught signal: SIGSEGV
Stack trace:
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5 : ()+0x95b84 [0x7fbaa50cfb84]
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5 : ()+0x94c49 [0x7fbaa50cec49]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5 : QObject::event(QEvent*)+0xe2 [0x7fbaa4d94072]
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 : QApplicationPrivate::notify_helper(QObject*, QEvent*)+0x81 [0x7fbaa595e4c1]
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 : QApplication::notify(QObject*, QEvent*)+0x210 [0x7fbaa5965970]
qbittorrent : Application::notify(QObject*, QEvent*)+0x22 [0x55764ff28c42]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5 : QCoreApplication::notifyInternal2(QObject*, QEvent*)+0x179 [0x7fbaa4d6a489]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5 : QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*)+0x1cb [0x7fbaa4d6d46b]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5 : ()+0x2bc103 [0x7fbaa4dbc103]
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 : g_main_context_dispatch()+0x2ae [0x7fbaa3a2ef2e]
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 : ()+0x4e1c8 [0x7fbaa3a2f1c8]
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 : g_main_context_iteration()+0x2c [0x7fbaa3a2f25c]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5 : QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag)+0x67 [0x7fbaa4dbb727]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5 : QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag)+0x13b [0x7fbaa4d6915b]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5 : QThread::exec()+0xb6 [0x7fbaa4bb8e76]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5 : ()+0xc2a67 [0x7fbaa4bc2a67]
/lib/x86_64-linux-gnu/libpthread.so.0 : ()+0x7fa3 [0x7fbaa4ae6fa3]
/lib/x86_64-linux-gnu/libc.so.6 : clone()+0x3f [0x7fbaa46f44cf]
Segmentation fault
@thalieht commented on GitHub (Feb 5, 2020):
Duplicate of #9667
@vlijmenfileer commented on GitHub (Feb 5, 2020):
I'm not certain how this is a duplicate of #9667, unless that one really is intended as a collection for any seemingly random crash, rather than the search-plugin triggered crashes towards I felt it had developed.
For me at least, this crash is triggered in a different way than the search-plugin crash.
@thalieht commented on GitHub (Feb 5, 2020):
The stacktrace is the same. Also FYI i haven't seen a similar crash report in a while (and there were ALOT). It was probably fixed in some later Qt version or perhaps even in qBt after 4.2.0.