qBittorrent has crashed (resuming after suspend)

[typhoon71]

qBittorrent & operating system versions

qBittorrent: 4.4.2 x64
Operating system: Windows 7 SP1 x64
Qt: 5.15.2
libtorrent-rasterbar: 2.0.5.0 (from info window, named libtorrent only)

What is the problem?

qBittorrent crashes upon resuming from suspension, see crash msg below:

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 7 Version 6.1 (Build 7601: SP 1) 6.1.7601 x86_64

Caught signal: SIGABRT

#  0 qbittorrent.exe      0x000000013fea99ec straceWin::getBacktrace()[ app\stacktrace_win.h : 220 ]
#  1 qbittorrent.exe      0x000000013feaab6b sigAbnormalHandler(signum)[ app\main.cpp : 368 ]
#  2 qbittorrent.exe      0x0000000140cda365 raise(signum)[ minkernel\crts\ucrt\src\appcrt\misc\signal.cpp : 541 ]
#  3 qbittorrent.exe      0x0000000140ce6a94 abort()[ minkernel\crts\ucrt\src\appcrt\startup\abort.cpp : 64 ]
#  4 qbittorrent.exe      0x0000000140cddd73 terminate()[ minkernel\crts\ucrt\src\appcrt\misc\terminate.cpp : 58 ]
#  5 qbittorrent.exe      0x0000000140cb51b7 __scrt_unhandled_exception_filter(pointers)[ d:\agent\_work\1\s\src\vctools\crt\vcstartup\src\utility\utility_desktop.cpp : 91 ]
#  6 kernel32.dll         0x000000007725ba20 UnhandledExceptionFilter()
#  7 ntdll.dll            0x0000000077359015 longjmp()
#  8 ntdll.dll            0x0000000077337388 _C_specific_handler()
#  9 ntdll.dll            0x000000007734bf7d _chkstk()
# 10 ntdll.dll            0x000000007732043a RtlInitializeResource()
# 11 ntdll.dll            0x0000000077323c3f RtlRaiseException()
# 12 KERNELBASE.dll       0x000007fefd18be0d RaiseException()
# 13 qbittorrent.exe      0x0000000140cd3611 _CxxThrowException(pExceptionObject, pThrowInfo)[ d:\agent\_work\1\s\src\vctools\crt\vcruntime\src\eh\throw.cpp : 129 ]
# 14 qbittorrent.exe      0x000000013fea279b boost::throw_exception(e)[ g:\qbittorrent\boost_1_78_0\boost\throw_exception.hpp : 148 ]
# 15 qbittorrent.exe      0x000000013fe9c8ed boost::asio::detail::do_throw_error(err, location)[ g:\qbittorrent\boost_1_78_0\boost\asio\detail\impl\throw_error.ipp : 38 ]
# 16 qbittorrent.exe      0x00000001401d929e boost::asio::detail::socket_select_interrupter::open_descriptors()[ g:\qbittorrent\boost_1_78_0\boost\asio\detail\impl\socket_select_interrupter.ipp : 66 ]
# 17 qbittorrent.exe      0x00000001401d9e3e boost::asio::detail::select_reactor::run(usec, ops)[ g:\qbittorrent\boost_1_78_0\boost\asio\detail\impl\select_reactor.ipp : 266 ]
# 18 qbittorrent.exe      0x00000001401da099 boost::asio::detail::select_reactor::run_thread()[ g:\qbittorrent\boost_1_78_0\boost\asio\detail\impl\select_reactor.ipp : 303 ]
# 19 qbittorrent.exe      0x00000001401726cf boost::asio::detail::win_thread_function(arg)[ g:\qbittorrent\boost_1_78_0\boost\asio\detail\impl\win_thread.ipp : 119 ]
# 20 qbittorrent.exe      0x0000000140ce64a0 thread_start(parameter)[ minkernel\crts\ucrt\src\appcrt\startup\thread.cpp : 115 ]
# 21 kernel32.dll         0x00000000771d555d BaseThreadInitThunk()
# 22 ntdll.dll            0x000000007733385d RtlUserThreadStart()

Steps to reproduce

1. from a browser: click on a magnet url
2. let qBittorrent load the torrent data (while still in the load torrent window)
3. leave it like on that window for a while (half an hour?)
4. suaspend the PC
5. resume from suspend
6. you get the crash info windows (qBittorrent has crashed...)

Additional context

Bittorrent crashes every time I suspend my PC, so usually I remember to close it before suspending.
This is the first time it crashed and I got to see the crash info window.

Log(s) & preferences file(s)

No response

[typhoon71]

Preferences file: qBittorrent.ini.txt

Log file: not present

[ghost]

This is a pretty old issue and there’s probably a few more tickets describing the same symptoms and a similar stacktrace. I think it has something to do with the network adapter being knocked off when going to sleep.
@arvidn any thoughts?

[thalieht]

Duplicate of #17082

[typhoon71]

Issue #17082 was opened after this one, so shouldn't the duplicate be the other one instead? Just asking.

[thalieht]

Issue #17082 was opened after this one, so shouldn't the duplicate be the other one instead? Just asking.

Normally yes but that issue has dev's attention.