-
-
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
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? |
this happens when something prevents a loopback socket from being created (specifically the interrupter socket in boost.asio). possibly by some firewall software. |
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 ? |
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: