-
-
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
Reporting Crash Bug as ordered. Happened the same last night but clicked wrong and lost the report. #19791
Comments
Once again... |
I saw it happen this time. It was my VPN reconnecting after it dropped out. FastestVPN with QT connected to the virtual FastestVPN network interface. Hope that helps some one. |
@glassez is there an upstream ticket ? |
|
@glassez We currently have 7 x Open Issues of boost::asio::detail::socket_select_interrupter::open_descriptors, which one would you like to keep open for easier keeping track of so that we can close the rest as duplicates? Same question for the 4 x Open Issues of alcohol 120% related incompatibility/conflict. |
I don't care. Do as you think will be better. Maybe it makes sense to leave open those of them where there is more useful information. |
Ok, will look after these later. |
Duplicate of #17082 |
qBittorrent & operating system versions
qBittorrent version: v4.6.0 (64-bit)
Libtorrent version: 1.2.19.0
Qt version: 6.4.3
Boost version: 1.83.0
OpenSSL version: 1.1.1w
zlib version: 1.3
OS version: Windows 11 Version 22H2 10.0.22621 x86_64
What is the problem?
qBittorrent has crashed
Please file a bug report at https://bugs.qbittorrent.org and provide the following information:
qBittorrent version: v4.6.0 (64-bit)
Libtorrent version: 1.2.19.0
Qt version: 6.4.3
Boost version: 1.83.0
OpenSSL version: 1.1.1w
zlib version: 1.3
OS version: Windows 11 Version 22H2 10.0.22621 x86_64
Caught signal: SIGABRT
Steps to reproduce
Additional context
This is a fresh install of the OS and the only version of QT that has ever been on it.
Log(s) & preferences file(s)
No response
The text was updated successfully, but these errors were encountered: