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

qBittorrent crashed unexpectedly #8260

Closed
bkvamme opened this Issue Jan 12, 2018 · 3 comments

Comments

Projects
None yet
3 participants
@bkvamme

bkvamme commented Jan 12, 2018

Please provide the following information

qBittorrent version and Operating System

v3.3.16 (64-bit), Windows 7 64bit

If on linux, libtorrent and Qt version

(type here)

What is the problem

qBittorrent crashed unexpectedly

What is the expected behavior

It does not crash.

Steps to reproduce

No idea, happened on a headless computer.

Extra info(if any)

#  0 qbittorrent.exe      0x000000013f8bd2d9 boost::asio::ssl::context::native_handle()
#  1 qbittorrent.exe      0x000000013f8c0adc boost::asio::ssl::context::native_handle()
#  2 qbittorrent.exe      0x0000000140361de1 boost::asio::ssl::rfc2818_verification::match_pattern()
#  3 qbittorrent.exe      0x0000000140426173 boost::asio::ssl::rfc2818_verification::match_pattern()
#  4 qbittorrent.exe      0x0000000140345ef0 boost::asio::ssl::rfc2818_verification::match_pattern()
#  5 ntdll.dll            0x000000007787812d RtlDecodePointer()
#  6 ntdll.dll            0x000000007786855f RtlUnwindEx()
#  7 ntdll.dll            0x000000007789bcb8 KiUserExceptionDispatcher()
#  8 qbittorrent.exe      0x0000000140190850 boost::asio::ssl::rfc2818_verification::match_pattern()
#  9 qbittorrent.exe      0x000000013f8d3f65 boost::asio::ssl::context::native_handle()
# 10 qbittorrent.exe      0x000000013f8d3cd8 boost::asio::ssl::context::native_handle()
# 11 qbittorrent.exe      0x000000013fa31dab boost::asio::ssl::detail::engine::native_handle()
# 12 qbittorrent.exe      0x00000001401722ed boost::asio::ssl::rfc2818_verification::match_pattern()
# 13 qbittorrent.exe      0x00000001400f02ee boost::asio::ssl::rfc2818_verification::match_pattern()
# 14 qbittorrent.exe      0x00000001400ef379 boost::asio::ssl::rfc2818_verification::match_pattern()
# 15 qbittorrent.exe      0x000000014013e986 boost::asio::ssl::rfc2818_verification::match_pattern()
# 16 qbittorrent.exe      0x000000013fd1f7cb boost::asio::ssl::rfc2818_verification::match_pattern()
# 17 qbittorrent.exe      0x000000013fd1f0a3 boost::asio::ssl::rfc2818_verification::match_pattern()
# 18 qbittorrent.exe      0x000000013f8b96f8 boost::asio::ssl::context::native_handle()
# 19 qbittorrent.exe      0x00000001401a6533 boost::asio::ssl::rfc2818_verification::match_pattern()
# 20 qbittorrent.exe      0x0000000140277dce boost::asio::ssl::rfc2818_verification::match_pattern()
# 21 USER32.dll           0x0000000077649bbd TranslateMessageEx()
# 22 USER32.dll           0x00000000776498c2 TranslateMessage()
# 23 qbittorrent.exe      0x0000000140279056 boost::asio::ssl::rfc2818_verification::match_pattern()
# 24 qbittorrent.exe      0x000000013fc86bf9 boost::asio::ssl::rfc2818_verification::match_pattern()
# 25 qbittorrent.exe      0x000000014027c9f6 boost::asio::ssl::rfc2818_verification::match_pattern()
# 26 qbittorrent.exe      0x000000013f8b937a boost::asio::ssl::context::native_handle()
# 27 qbittorrent.exe      0x000000013f8c03ed boost::asio::ssl::context::native_handle()
# 28 qbittorrent.exe      0x0000000140327c57 boost::asio::ssl::rfc2818_verification::match_pattern()
# 29 qbittorrent.exe      0x0000000140342ed7 boost::asio::ssl::rfc2818_verification::match_pattern()
# 30 kernel32.dll         0x00000000777459cd BaseThreadInitThunk()
# 31 ntdll.dll            0x000000007787a561 RtlUserThreadStart()
@FranciscoPombal

This comment has been minimized.

Show comment
Hide comment
@FranciscoPombal

FranciscoPombal Jan 16, 2018

Contributor

Can you reproduce this issue in the newest version, 4.0.3? I think the 3.x branches are no longer maintained. The solution would be to upgrade

Contributor

FranciscoPombal commented Jan 16, 2018

Can you reproduce this issue in the newest version, 4.0.3? I think the 3.x branches are no longer maintained. The solution would be to upgrade

@bkvamme

This comment has been minimized.

Show comment
Hide comment
@bkvamme

bkvamme Jan 17, 2018

bkvamme commented Jan 17, 2018

@FranciscoPombal

This comment has been minimized.

Show comment
Hide comment
@FranciscoPombal

FranciscoPombal Jan 17, 2018

Contributor

@bkvamme That is good to hear. If you encounter another problem with the new version please open a new issue for it. This one can be closed.

Contributor

FranciscoPombal commented Jan 17, 2018

@bkvamme That is good to hear. If you encounter another problem with the new version please open a new issue for it. This one can be closed.

@thalieht thalieht added the Crash label Jul 25, 2018

@thalieht thalieht closed this Jul 28, 2018

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