-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Crash Report. 20th+ crash of the day. Crashes every 5-60 min. #17082
Comments
Logs and ini |
Looks like some network related exception is unhandled by libtorrent. |
this looks like an internal boost.asio thread, and it looks like it's failing to bind a socket to the IPv4 loopback address, port 0 (which means the OS gets to pick the port). I think this is never really expected to fail. |
Also I am using a VPN for qbittorent called Windscribe. Spit tunneling in inclusive mode. Not sure if this is effecting anything. |
I am using the exact same thing (Windscribe. Spit tunneling) and have the exact same issue. |
Can you reproduce the crash if you disable UPnP and Local service discovery from qbittorrent? If not then it may be a temporary solution till it gets fixed upstream. |
I don't have UPnP or local discovery enabled and still have the issue. |
Is it possible that qBt enables UPnP and LSD for a split second before loading the config and disabling it? If so, changing settings wouldn't affect this issue. |
I found this in the code. Seems like libtorrent enables those by default and qbit attempts to disable them at startup. qBittorrent/src/base/bittorrent/session.cpp Line 1379 in 5b269a7
|
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
qBittorrent applies settings at |
This comment was marked as outdated.
This comment was marked as outdated.
This will more than likely miss being included in upcoming Boost 1.80 release. (libtorrent) Adhering to advise from |
Could someone test a build with this patch applied to libtorrent? arvidn/libtorrent#6994 This is against libtorrent-1.2.x right now, I will forward-port it once it lands. |
Windows test build based on qBittorrent https://github.com/xavier2k6/qBittorrent/suites/7701493068/artifacts/322063548 |
@Quest79 @electricmessiah Can you try build in #17082 (comment) & provide feedback please? |
I started encountering this bug myself recently, two weeks ago and again now: qBittorrent version: v4.6.5 (64-bit) Caught signal: SIGABRT
|
I still get this, but not as often now that im on slightly more stable internet. Maybe 1 time every day now usually when I wake up and check it. For me Im 90% certain it has something to do with my VPN client losing connection and reconnecting or connecting to a different host. VPN will alter its virtual network controller somehow and qBit will get very very confused and flip out rather than just elegantly chill and reconnect when needed. Im using Windscribe 2.10.16 and the latest qBit. |
I just got this crash again. qBittorrent version: v4.6.5 (64-bit) Caught signal: SIGABRT
|
any idea what firewall software ? Can we compile a list ? |
@cappelikan your crash report is not the same as the one described in this ticket & is also a forked version "enhanced edition" which we do not support. |
The v5.0.0 is running flawless so far, fingers crossed. Its still too early to give an opinion with the extremely low frequency of the situation. |
qBittorrent has crashed qBittorrent version: v5.0.0 (64-bit) Caught signal: SIGABRT
All I did was restart my VPN. |
Its not about frequency, its about repeatability. This reliably crashes when it loses VPN connection or a VPN closes a connection. Instead of going into a wait state of some sort qbt (or a lib it uses?) just apparently has no graceful way to deal with it and crashes instead. |
You should read though the report thread before suggesting things. |
Ok, will read again and remove my previous comment. It doesn't change the fact that recently mentioning "loosing connection" and another users "restarting VPN" is too vague and doesn't guarantee to crash my qBittorrent. So there should have been more written in recent comments to get everyone reliably reproduce to avoid a need to guess or to read the whole thread. |
@qBittUser I could reliably re-produce this crash over & over using cloudflare warp program....then there was an update & haven't been able to reliably re-produce anymore.....there are less & lees users experiencing this issue & unfortunately for @Quest79 it remains consistent & we still haven't been able to ascertain a fix that will cater for all/eradicate this very annoying crash. |
@Quest79 Are you still on windscribe 2.10.16 or latest 2.11.11? |
Regarding the repeatability:
I could pretty much reproduce it on demand also (this by messing with ProtonVPN in a way). But reliable "triggering" it for investigation as of this day I don't find / come across anymore no. |
@xavier2k6 As long as I've been using WireGuard and Cloudflare WARP, the client has never crashed. Are there clear steps to reproduce? |
I had a consistent/reproducible step(s) in #18811 (comment) but then the app got an update & could never reproduce. |
qBittorrent & operating system versions
qBittorrent version: v4.4.2 (64-bit)
Libtorrent version: 2.0.5.0
Qt version: 5.15.2
Boost version: 1.78.0
OpenSSL version: 1.1.1n
zlib version: 1.2.11
OS version: Windows 10 Version 2009 10.0.22000 x86_64 (This is windows 11 why is this app reporting windows 10?)
Caught signal: SIGABRT
What is the problem?
qBittorrent has crashed
Please file a bug report at http://bugs.qbittorrent.org and provide the following information:
qBittorrent version: v4.4.2 (64-bit)
Libtorrent version: 2.0.5.0
Qt version: 5.15.2
Boost version: 1.78.0
OpenSSL version: 1.1.1n
zlib version: 1.2.11
OS version: Windows 10 Version 2009 10.0.22000 x86_64
Caught signal: SIGABRT
Steps to reproduce
Additional context
Nothing else on my system network related or otherwise is crashing (online games included). I have a feeling it is crashing every time my wifi is interrupted. So instead of just neatly allowing for sudden connection loss, it just flat out freaks out and dies? A wild guess as I have no other ideas.
This is a fresh (few days old) install of windows 11 22000.
Log(s) & preferences file(s)
No response
The text was updated successfully, but these errors were encountered: