-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Random crashes #9667
Comments
Removing the package |
same issue `qBittorrent version: v4.1.3 Caught signal: SIGSEGV |
Which distro are you using?
…On Fri, Oct 12, 2018, 2:14 PM mohamedation ***@***.***> wrote:
same issue
`qBittorrent version: v4.1.3
Caught signal: SIGSEGV
Stack trace:
/usr/lib/libQt5Network.so.5 : ()+0x9aca4 [0x7f60c2bceca4]
/usr/lib/libQt5Network.so.5 : ()+0x9959b [0x7f60c2bcd59b]
/usr/lib/libQt5Core.so.5 : QObject::event(QEvent*)+0xe2 [0x7f60c288f352]
/usr/lib/libQt5Widgets.so.5 : QApplicationPrivate::notify_helper(QObject*,
QEvent*)+0x84 [0x7f60c3452e14]
/usr/lib/libQt5Widgets.so.5 : QApplication::notify(QObject*,
QEvent*)+0x211 [0x7f60c345a6e1]
qbittorrent : Application::notify(QObject*, QEvent*)+0x23 [0x55a21c2b6b43]
/usr/lib/libQt5Core.so.5 : QCoreApplication::notifyInternal2(QObject*,
QEvent*)+0x179 [0x7f60c2864c39]
/usr/lib/libQt5Core.so.5 :
QCoreApplicationPrivate::sendPostedEvents(QObject*, int,
QThreadData*)+0x1dc [0x7f60c2867ccc]
/usr/lib/libQt5Core.so.5 : ()+0x2c59d4 [0x7f60c28b89d4]
/usr/lib/libglib-2.0.so.0 : g_main_context_dispatch()+0x2bf
[0x7f60c15103cf]
/usr/lib/libglib-2.0.so.0 : ()+0x6cf89 [0x7f60c1511f89]
/usr/lib/libglib-2.0.so.0 : g_main_context_iteration()+0x2e
[0x7f60c1511fce]
/usr/lib/libQt5Core.so.5 :
QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag)+0x69
[0x7f60c28b7fc9]
/usr/lib/libQt5Core.so.5 :
QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag)+0x13c [0x7f60c28638cc]
/usr/lib/libQt5Core.so.5 : QThread::exec()+0xb9 [0x7f60c26aceb9]
/usr/lib/libQt5Core.so.5 : ()+0xc3f65 [0x7f60c26b6f65]
/usr/lib/libpthread.so.0 : ()+0x7a9d [0x7f60c25d9a9d]
/usr/lib/libc.so.6 : clone()+0x43 [0x7f60c21d9a43]
[1] 23910 segmentation fault (core dumped) qbittorrent
`
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#9667 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMdf7fzYas8skjStk2tetrVCk4zrUsw8ks5ukFZ_gaJpZM4XTG1h>
.
|
Arch Linux |
did removing |
I haven't try, but I don't think the fix should be removing packages. |
Same issue here, also on Arch Linux.
|
still no clue? |
Stacktraces are useless for debugging, happens only in Arch. Why don't you report that to the Arch bug tracker or build qt5-base with debugging enabled? |
Crashes on blackPanther OS as well... In cmdline:
Backtrace
|
@blackPantherOS: your backtrace differs from that in the first post and looks very similar to those in #9485. |
|
No, of course it is not. Do you see any difference between your one and those posted earlier, except for the GDB UI messages and explicit frame numbers? |
Can you tell me how Can I get the qbittorrent's backtrace?What is the command? |
@zoggee: if you are using Arch too, please check out the Arch wiki: https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces |
@zeule > @blackPantherOS: your backtrace differs from that in the first post and looks very similar to those in #9485. Yes, the disabled c++11 solved this crash problem. |
@blackPantherOS ,I can't figure it out.Could you show me how can I fix it?Plus,My English aint so good. |
@zeule Ok,I get it.I just want to know if whether it have another way to get backtrace or not(My English isn't so good,forgive me).Thank you very much! |
|
@zoggee, ignore that reply above. @blackPantherOS, please put attention to the context. Your problem is not the same as people here are discussing. @zoggee if you want a help, applicable in your case, please tell us the name of your distribution. |
@zeule OK. |
$ pacman -Qi qt5-base |
Thank you. Then please follow the link to the Arch Wiki. In this particular case this section seems to provide the simples way to achieve the goal. |
@zeule No,thank you. Should I uninstall the qt5-base and install the qt-debug packages with debug symbols in order to get the backtrace without lost function name? (I'm a newbie for linux user and compiler.) |
@zoggee I think you only need the qt5-base-debug package and whatever this package requires to install or replace. |
OK,I'll try my best. Thank you very much. Can I ask blackPantherOS another question? |
|
@zeule When I type qbittorrent in comand line,I've got the warning message below: Is it matter with the crash? |
qBittorrent version: v4.1.8 (64-bit) Caught signal: SIGSEGV
|
i'm getting this on Debian 10, a few seconds after starting. i don't know what broke it. it worked earlier today, and i don't remember changing anything, nor adding any new torrents. i may have updated some packages, but i don't remember extensive updates, nor qt libs. 4.1.3 crashes the same as 4.1.7 from testing.
|
Try disabling RSS. |
Latest Git (4.2.0 beta) is very stable. No crashes in last two hours... |
packagekit-qt5 not installed
|
I think I have managed to correct this bug on my Debian 10 system by compiling (4.1.9.1) with a newer QT version (5.12.6). qBittorrent still reports version 5.11.3 which I can only guess is because of the environment. Also: I was running qBittorrent 4.1.5 in Debian 9 (Qt 5.7.1). Upgrading to Debian 10 (the same version of qBittorrent with Qt 5.11.3) broke it and I got these segfaults whenever I tried to load the fastresume data (not with a clean data/qBittorrent folder). Don't know if it's relevant, but I also switched from XFCE to KDE in the process. |
I have the same. To be precise, the crash is triggered by going to the search tab, and then opening the Search plugins window. Seeing how it started apparently randomly, and no critical packages had been updated or installed when it happened, I suspected the search plugins themselves, which I had recently updated.
My guess is the problem is in an update to one these random (default?, official?) plugins. qBittorrent v4.1.5 (64-bit) I never use(d) the RSS option. OS: Debian GNU/Linux 10 (buster) x86_64 |
Hi, I have the same issue. qBittorrent version and Operating System If on linux, libtorrent-rasterbar and Qt version What is the problem What is the expected behavior(type here) Steps to reproduce Extra info(if any) Caught signal: SIGSEGV |
Thanks to all for the reports. However, all crash reports here are from very old versions at this point. The root casue of these crashes has most likely been fixed in libtorrent/Qt/boost, etc. Submit a new issue if you have any problems with 4.2.3, the latest version. |
Note: this problem seems to be related to Qt 5.11.3 and the usage of specific search plugins, or the tracker favicons in older Qt versions. If you're on Windows or macOS, the most recent builds have been shipping with more recent versions for a long time now. On Linux, here are some possible workarounds, if you're stuck on that Qt version:
|
qBittorrent version and Operating System
qBittorrent version: v4.1.3
Arch Linux
If on linux, libtorrent and Qt version
Name : linux
Version : 4.18.12.arch1-1
Name : qt5-base
Version : 5.11.2-1
Name : libtorrent-rasterbar
Version : 1:1.1.10-1
What is the problem
Opens, crashes if GUI is open after about 5 seconds. Downloads fine during the mean time.
What is the expected behavior
Shouldn't close.
Steps to reproduce
Just open it up and wait.
Extra info(if any)
Worked fine a couple of hours ago.
The text was updated successfully, but these errors were encountered: