Skip to content
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

Repeated crashes #21108

Closed
tpapictures opened this issue Jul 23, 2024 · 8 comments
Closed

Repeated crashes #21108

tpapictures opened this issue Jul 23, 2024 · 8 comments

Comments

@tpapictures
Copy link

qBittorrent & operating system versions

qBittorrent version: v4.6.5 (64-bit)
Libtorrent version: 1.2.19.0
Qt version: 6.4.3
Boost version: 1.85.0
OpenSSL version: 1.1.1w
zlib version: 1.3.1
OS version: Windows 6.2 6.2.9200 x86_64

What is the problem?

Caught signal: SIGABRT

 0# boost::stacktrace::basic_stacktrace >::init at G:\QBITTORRENT\boost_1_85_0\boost\stacktrace\stacktrace.hpp:91
 1# getStacktrace at G:\QBITTORRENT\qbt-src-4.6.5\src\app\stacktrace.cpp:35
 2# `anonymous namespace'::abnormalExitHandler at G:\QBITTORRENT\qbt-src-4.6.5\src\app\signalhandler.cpp:104
 3# raise at minkernel\crts\ucrt\src\appcrt\misc\signal.cpp:547
 4# abort at minkernel\crts\ucrt\src\appcrt\startup\abort.cpp:71
 5# terminate at minkernel\crts\ucrt\src\appcrt\misc\terminate.cpp:58
 6# FindHandler at D:\a\_work\1\s\src\vctools\crt\vcruntime\src\eh\frame.cpp:735
 7# __InternalCxxFrameHandler at D:\a\_work\1\s\src\vctools\crt\vcruntime\src\eh\frame.cpp:399
 8# __InternalCxxFrameHandlerWrapper at D:\a\_work\1\s\src\vctools\crt\vcruntime\src\eh\frame.cpp:234
 9# __CxxFrameHandler4 at D:\a\_work\1\s\src\vctools\crt\vcruntime\src\eh\risctrnsctrl.cpp:306
10# _chkstk in ntdll
11# RtlRaiseException in ntdll
12# RtlRaiseException in ntdll
13# RaiseException in KERNELBASE
14# _CxxThrowException at D:\a\_work\1\s\src\vctools\crt\vcruntime\src\eh\throw.cpp:75
15# boost::throw_exception at G:\QBITTORRENT\boost_1_85_0\boost\throw_exception.hpp:157
16# boost::asio::detail::do_throw_error at G:\QBITTORRENT\boost_1_85_0\boost\asio\detail\impl\throw_error.ipp:42
17# boost::asio::detail::socket_select_interrupter::open_descriptors at G:\QBITTORRENT\boost_1_85_0\boost\asio\detail\impl\socket_select_interrupter.ipp:66
18# boost::asio::detail::select_reactor::restart_reactor::do_complete at G:\QBITTORRENT\boost_1_85_0\boost\asio\detail\impl\select_reactor.ipp:343
19# boost::asio::detail::win_iocp_io_context::do_one at G:\QBITTORRENT\boost_1_85_0\boost\asio\detail\impl\win_iocp_io_context.ipp:476
20# boost::asio::detail::win_iocp_io_context::run at G:\QBITTORRENT\boost_1_85_0\boost\asio\detail\impl\win_iocp_io_context.ipp:206
21# std::thread::_Invoke >,0> at C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.34.31933\include\thread:55
22# thread_start at minkernel\crts\ucrt\src\appcrt\startup\thread.cpp:97
23# BaseThreadInitThunk in KERNEL32
24# RtlUserThreadStart in ntdll

Steps to reproduce

No response

Additional context

No response

Log(s) & preferences file(s)

No response

@thalieht
Copy link
Contributor

Duplicate of #17082

@thalieht thalieht marked this as a duplicate of #17082 Jul 23, 2024
@thalieht thalieht closed this as not planned Won't fix, can't repro, duplicate, stale Jul 23, 2024
@xavier2k6
Copy link
Member

xavier2k6 commented Jul 23, 2024

OS version: Windows 6.2 6.2.9200 x86_64

This OS is no longer supported by us & official installer dialog would've displayed a warning.

@tpapictures
Copy link
Author

tpapictures commented Jul 26, 2024 via email

@xavier2k6
Copy link
Member

I’m on Windows 10 I’m not on that version you listed.

Well, that's the version you provided in your crash report

@tpapictures
Copy link
Author

tpapictures commented Jul 30, 2024 via email

@xavier2k6
Copy link
Member

@tpapictures no need, your crash is a duplicate of known issue anyway.

@tpapictures
Copy link
Author

@tpapictures no need, your crash is a duplicate of known issue anyway.

How do I search for the known issue if I don't know what the known issue is called?
So if it's a known issue, then what is the solution, to run a previous build?

@xavier2k6
Copy link
Member

How do I search for the known issue if I don't know what the known issue is called?

Already provided in #21108 (comment)

So if it's a known issue, then what is the solution, to run a previous build?

Previous builds have also have had the issue, it's a long-standing issue that hasn't been narrowed down/fixed yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants