mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Random crashes #7888
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#7888
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 @clasick on GitHub (Oct 9, 2018).
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.
@clasick commented on GitHub (Oct 9, 2018):
Removing the package
packagekit-qt5seems to fix the issue.@mohamedation commented on GitHub (Oct 12, 2018):
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
`
@clasick commented on GitHub (Oct 13, 2018):
Which distro are you using?
On Fri, Oct 12, 2018, 2:14 PM mohamedation notifications@github.com wrote:
@mohamedation commented on GitHub (Oct 14, 2018):
Arch Linux
@clasick commented on GitHub (Oct 15, 2018):
did removing
packagekit-qt5fix your crashes?@mohamedation commented on GitHub (Oct 17, 2018):
I haven't try, but I don't think the fix should be removing packages.
@zeromind commented on GitHub (Nov 1, 2018):
Same issue here, also on Arch Linux.
packagekit-qt5is not installed.@mohamedation commented on GitHub (Nov 9, 2018):
still no clue?
@zeule commented on GitHub (Nov 9, 2018):
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?
@blackPantherOS commented on GitHub (Nov 11, 2018):
Crashes on blackPanther OS as well...
rastebar 1.1.10 (crash with 1.1.9 too)
qt 5.11
In cmdline:
Backtrace
@zeule commented on GitHub (Nov 12, 2018):
@blackPantherOS: your backtrace differs from that in the first post and looks very similar to those in #9485.
@zoggee commented on GitHub (Nov 12, 2018):
@zeule commented on GitHub (Nov 12, 2018):
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?
@zoggee commented on GitHub (Nov 12, 2018):
Can you tell me how Can I get the qbittorrent's backtrace?What is the command?
@zeule commented on GitHub (Nov 13, 2018):
@zoggee: if you are using Arch too, please check out the Arch wiki: https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces
@blackPantherOS commented on GitHub (Nov 13, 2018):
@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.
Thanks
@zoggee commented on GitHub (Nov 13, 2018):
@blackPantherOS ,I can't figure it out.Could you show me how can I fix it?Plus,My English aint so good.
Thank you very much!
@zoggee commented on GitHub (Nov 13, 2018):
@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!
@blackPantherOS commented on GitHub (Nov 13, 2018):
of course. the highlighted line the important row
@zeule commented on GitHub (Nov 13, 2018):
@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.
@zoggee commented on GitHub (Nov 13, 2018):
@zeule OK.
My distribution is ArchLinux
$uname -a
4.18.16-arch1-1-ARCH #1 SMP PREEMPT Sat Oct 20 22:06:45 UTC 2018 x86_64 GNU/Linux
qBittorrent version: v4.1.3
@zoggee commented on GitHub (Nov 13, 2018):
$ pacman -Qi qt5-base
名字 : qt5-base
版本 : 5.11.2-1
描述 : A cross-platform application and UI framework
架构 : x86_64
@zeule commented on GitHub (Nov 13, 2018):
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.
@zoggee commented on GitHub (Nov 13, 2018):
@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.)
@zeule commented on GitHub (Nov 13, 2018):
@zoggee I think you only need the qt5-base-debug package and whatever this package requires to install or replace.
@zoggee commented on GitHub (Nov 13, 2018):
OK,I'll try my best. Thank you very much. Can I ask blackPantherOS another question?
@zoggee commented on GitHub (Nov 13, 2018):
@zoggee commented on GitHub (Nov 19, 2018):
@zeule When I type qbittorrent in comand line,I've got the warning message below:
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
Is it matter with the crash?
How Can I set the variable?
@ideal commented on GitHub (Nov 20, 2018):
This is a warning and may not related with the crash.
If you want to set QT_QPA_PLATFORM, either
export QT_QPA_PLATFORM=waylandand then start qbittrorrent, or addexport QT_QPA_PLATFORM=waylandto your .bashrc (if you are using bash).@zoggee commented on GitHub (Nov 21, 2018):
@ideal thank you!
@zeule ,I delete the configuration file 'qBittorrent.conf' location in ~/.config/qBittorrent,it seems save the crash.
I remember that I've add the trackers list into my qbittorent before the crash.It means I can't do that any more??
@txtsd commented on GitHub (Nov 24, 2018):
Seems this happens once RSS feeds trigger. If there is no internet connection, it doesn't crash at all.
@iiv3 commented on GitHub (Nov 27, 2018):
I'm also hitting the original problem with a specific torrent.
It crashes qBittorrent on startup even when that torrent is paused. It doesn't crash if internet is down.
It seems that the problem is related to querying trackers.
By removing trackers and try-error-guess method I was able to limit the list of trackers to two.
This specific torrent has 3 trackers that are using
https://. When having only#1and#3trackers there is a crash. When having only#2and#3there is a crash.(Sometimes there is no crash, but that's rare.)
Using
wiresharkI can see that tracker#3is queried first. I open TCP to him, it confirms with zero-length packet, I sendTLSv1 "Client Hello"packet. Then my host sends DNS query for the next tracker, gets reply and sendsTCP SYNto it. Then tracker#3replies with zero-length packet havingFIN, I reply withFIN. Then I get twoRSTpackets from him.(Then I get
TCP SYNreply from the second tracker, but I reply withRST. The program might have already crashed at that point.)I also tried running
qBittorrentundervalgrind. The (mildly) interesting part of the log is:The
objdumpdisassembler of the function that crashes looks like this:I'm on Slackware64-current, I compile my own Qt5, I do not strip it, but it's likely that the problem functions are private. Qt5 is linked to
libssl-1.1fromopenssl.I might be able to compile Qt5 debug build, it's just it is huge and takes quite a while.
I'll do that only if you can't reproduce the problem.
About private stuff, ask me in private.
@thalieht commented on GitHub (Dec 16, 2018):
Finally someone has a stacktrace with symbols https://github.com/qbittorrent/qBittorrent/issues/9607#issuecomment-447603610. Now someone can report it to Qt or arch.
@thalieht commented on GitHub (Jan 8, 2019):
and another https://github.com/qbittorrent/qBittorrent/issues/9714#issuecomment-432404101
@fluidvoice commented on GitHub (Jan 10, 2019):
I think it's premature to close this issue as duplicate. In my case the crash is happening based upon active torrents, so it doesn't look Qt/graphics related:
https://github.com/qbittorrent/qBittorrent/issues/10140#issuecomment-453102197
It's crashing randomly and the app just disappears. Also, after it crashes when restarted the previously in-progress downloads restart - revert back to zero bytes downloaded. I have over 2GB free RAM, so it's not low-memory related. I had only 4 torrents active, 3 paused and only 1 downloading. It has crashed at least 3 times like this in the past hour.
Edit: I just removed all paused torrents so now I only have one torrent downloading and it finally completed without crashing. Just luck? dunno.
$ lsb_release -a;pacman -Q linux qt5-base qbittorrent libtorrent-rasterbar packagekit-qt5
LSB Version: n/a
Distributor ID: ManjaroLinux
Description: Manjaro Linux
Release: 18.0.2
Codename: Illyria
linux414 4.14.91-1
qt5-base 5.12.0-1.1
qbittorrent 4.1.5-1
libtorrent-rasterbar 1:1.1.11-1
error: package 'packagekit-qt5' was not found
@chmuri commented on GitHub (Jan 23, 2019):
@here Solution fast check:
After that everything is OK On my side and QB starts normally better than 4.1.3! 🥇
@iiv3 commented on GitHub (Feb 17, 2019):
To avoid crashes at startup I do recommend turning off
Preferences->Advanced->qBittorrentSection->DownloadTrackerFavIcon.At startup qbittorrent would connect to the trackers of all torrents, even paused or complete, just to take their favicons. This increases the chance of triggering the QT5 bug.
@GongT commented on GitHub (Mar 27, 2019):
bt full:@sledgehammer999 commented on GitHub (Apr 7, 2019):
Those having crashes attributed to tracker favicon downloads: What is your tracker numbers? Is it high? (take a look at number shown in the sidepanel)
@Cqoicebordel commented on GitHub (Apr 7, 2019):
~241 (and removing the option to have favicons solved it for me)
@Fritigern commented on GitHub (Apr 7, 2019):
I have 140 trackers here.
@iiv3 commented on GitHub (Apr 8, 2019):
You can trigger the bug with just 3
httpstrackers.@Eaglemyoung commented on GitHub (Apr 9, 2019):
Please provide the following information
qBittorrent version and Operating System
qBittorrent version
version: v4.1.5
Operating System
Linux debian 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15) x86_64 GNU/Linux
If on linux, libtorrent and Qt version
libtorrent
libtorrent-rasterbar9 1.1.11-2
What is the problem
starting qbitorrent it crashes
(qbittorrent:10580): dbind-WARNING **: 23:06:18.131: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
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 : ()+0x95ba4 [0x7f1215269ba4]
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5 : ()+0x94c69 [0x7f1215268c69]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5 : QObject::event(QEvent*)+0xe2 [0x7f1214f2e182]
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 : QApplicationPrivate::notify_helper(QObject*, QEvent*)+0x81 [0x7f1215af94b1]
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 : QApplication::notify(QObject*, QEvent*)+0x210 [0x7f1215b00950]
qbittorrent : Application::notify(QObject*, QEvent*)+0x22 [0x56052c41ac42]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5 : QCoreApplication::notifyInternal2(QObject*, QEvent*)+0x179 [0x7f1214f045a9]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5 : QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*)+0x1cb [0x7f1214f0759b]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5 : ()+0x2bc233 [0x7f1214f56233]
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 : g_main_context_dispatch()+0x2ae [0x7f1213bc8f2e]
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 : ()+0x4e1c8 [0x7f1213bc91c8]
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 : g_main_context_iteration()+0x2c [0x7f1213bc925c]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5 : QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag)+0x63 [0x7f1214f55863]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5 : QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag)+0x13b [0x7f1214f0327b]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5 : QThread::exec()+0xb6 [0x7f1214d52ec6]
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5 : ()+0xc2aa7 [0x7f1214d5caa7]
/lib/x86_64-linux-gnu/libpthread.so.0 : ()+0x7fa3 [0x7f1214c80fa3]
/lib/x86_64-linux-gnu/libc.so.6 : clone()+0x3f [0x7f121488e82f]
What is the expected behavior
No
Steps to reproduce
when I add a torrent file on qbittorrent, it crashes.
and I use qbittorrent command on terminal.
qbittorrent can't startup, and throw the errors.
Extra info(if any)
No
Thank you
reinstall Qbittorrent?
@sledgehammer999 commented on GitHub (May 3, 2019):
Has anyone tried with Qt 5.12? Does it still crash there?
@Chocobo1 commented on GitHub (May 3, 2019):
Here is one: #10520
@Chocobo1 commented on GitHub (May 3, 2019):
Also noticed that all related reports that have in common is they are all using linux, didn't see macOS nor windows...
@sledgehammer999 commented on GitHub (May 5, 2019):
2 bug reports from debian bug tracker:
@servimo commented on GitHub (May 14, 2019):
To avoid crashes at startup I do recommend turning off
Preferences->Advanced->qBittorrentSection->DownloadTrackerFavIcon.
At startup qbittorrent would connect to the trackers of all torrents, even
paused or complete, just to take their favicons. This increases the chance
of triggering the QT5 bug.
Em ter, 14 de mai de 2019 03:44, gorvinsky notifications@github.com
escreveu:
@Piccirello commented on GitHub (Aug 14, 2019):
Did we ever figure out the cause of this? There are a lot of github issues being created.
@sledgehammer999 commented on GitHub (Aug 15, 2019):
Probably openssl > 1.0.x series
@iiv3 commented on GitHub (Aug 20, 2019):
It is definitely QT5 bug. Most likely a race condition. You need 2 https:// connections where the first one closes immediately, while the second one is been negotiated. Check my first report above.
@KozakaiAya commented on GitHub (Aug 23, 2019):
same issue here, I tried to turn off the TrackerFavicon option and it does not help. Then I got enlighted by #11046 and turned of the RSS fetch, the crash stops.
@statmonkey commented on GitHub (Sep 4, 2019):
Sorry posted in #11187 same issue.
@robert21281 commented on GitHub (Oct 7, 2019):
qBittorrent version: v4.1.8 (64-bit)
Libtorrent version: 1.1.13.0
Qt version: 5.13.1
Boost version: 1.71.0
OS version: Windows 10 (10.0) 10.0.18362 x86_64
Caught signal: SIGSEGV
@attila-lendvai commented on GitHub (Oct 10, 2019):
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.
@salmanulfarzy commented on GitHub (Oct 20, 2019):
Try disabling RSS.
@blackPantherOS commented on GitHub (Oct 22, 2019):
Latest Git (4.2.0 beta) is very stable. No crashes in last two hours...
@1noro commented on GitHub (Oct 30, 2019):
packagekit-qt5 not installed
@octopoisson commented on GitHub (Nov 25, 2019):
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.
@vlijmenfileer commented on GitHub (Dec 19, 2019):
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)
Qt: 5.11.3
Libtorrent: 1.1.11.0
Boost: 1.67.0
I never use(d) the RSS option.
OS: Debian GNU/Linux 10 (buster) x86_64
Model: Dell System XPS L502X
Kernel: 5.2.0-0.bpo.3-amd64
Shell: bash 5.0.3
Resolution: 1920x1080
DE: Xfce
WM: Xfwm4
WM Theme: Breeze
Theme: Breeze [GTK2/3]
Icons: Adwaita [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: 3574MiB / 7935MiB
@gonoloo commented on GitHub (Mar 31, 2020):
Hi, I have the same issue.
I'm quite a very beginner on debian and linux and I'm not good at all in code, so I need a lot of explanations about how solving this issue... Thanks :)
qBittorrent version and Operating System
qBittorrent 4.1.5 & Debian KDE plasma 5.14.5
If on linux, libtorrent-rasterbar and Qt version
libtorrent-rasterbar9 & Qt 5.11.3
What is the problem
qBittorrent is closing by itself just after I opened it (less than 1 second after). It happened just after I tried to add a lot of trackers to one torrent.
What is the expected behavior(type here)
Not closing
Steps to reproduce
Adding a lot of trackers ?
Extra info(if any)
qBittorrent version: v4.1.5
Caught signal: SIGSEGV
Stack trace:
/lib/x86_64-linux-gnu/libQt5Network.so.5 : ()+0x95b84 [0x7f14b097ab84]
/lib/x86_64-linux-gnu/libQt5Network.so.5 : ()+0x94c49 [0x7f14b0979c49]
/lib/x86_64-linux-gnu/libQt5Core.so.5 : QObject::event(QEvent*)+0xe2 [0x7f14b063f072]
/lib/x86_64-linux-gnu/libQt5Widgets.so.5 : QApplicationPrivate::notify_helper(QObject*, QEvent*)+0x81 [0x7f14b12094c1]
/lib/x86_64-linux-gnu/libQt5Widgets.so.5 : QApplication::notify(QObject*, QEvent*)+0x210 [0x7f14b1210970]
qbittorrent : Application::notify(QObject*, QEvent*)+0x22 [0x562abad92c42]
/lib/x86_64-linux-gnu/libQt5Core.so.5 : QCoreApplication::notifyInternal2(QObject*, QEvent*)+0x179 [0x7f14b0615489]
/lib/x86_64-linux-gnu/libQt5Core.so.5 : QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*)+0x1cb [0x7f14b061846b]
/lib/x86_64-linux-gnu/libQt5Core.so.5 : ()+0x2bc103 [0x7f14b0667103]
/lib/x86_64-linux-gnu/libglib-2.0.so.0 : g_main_context_dispatch()+0x2ae [0x7f14af2d9f2e]
/lib/x86_64-linux-gnu/libglib-2.0.so.0 : ()+0x4e1c8 [0x7f14af2da1c8]
/lib/x86_64-linux-gnu/libglib-2.0.so.0 : g_main_context_iteration()+0x2c [0x7f14af2da25c]
/lib/x86_64-linux-gnu/libQt5Core.so.5 : QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag)+0x67 [0x7f14b0666727]
/lib/x86_64-linux-gnu/libQt5Core.so.5 : QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag)+0x13b [0x7f14b061415b]
/lib/x86_64-linux-gnu/libQt5Core.so.5 : QThread::exec()+0xb6 [0x7f14b0463e76]
/lib/x86_64-linux-gnu/libQt5Core.so.5 : ()+0xc2a67 [0x7f14b046da67]
/lib/x86_64-linux-gnu/libpthread.so.0 : ()+0x7fa3 [0x7f14b0391fa3]
/lib/x86_64-linux-gnu/libc.so.6 : clone()+0x3f [0x7f14aff9f4cf]
Erreur de segmentation
@FranciscoPombal commented on GitHub (Apr 2, 2020):
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.
@FranciscoPombal commented on GitHub (Apr 8, 2020):
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: