qBittorrent v4.3.3 has crashed

[MewX]

qBittorrent version and Operating System

qBittorrent version: v4.3.3 (32-bit) Libtorrent version: 1.2.12.0 Qt version: 5.15.2 Boost version: 1.75.0 OpenSSL version: 1.1.1i zlib version: 1.2.11 OS version: Windows 10 Version 2009 10.0.19042 x86_64

Caught signal: SIGABRT

#  0 ???                  0x00000000003b9e21 0x003b9e21()
#  1 ???                  0x00000000003bad8a 0x003bad8a()
#  2 ???                  0x0000000000d72574 0x00d72574()
#  3 ???                  0x0000000000d7c72a 0x00d7c72a()
#  4 ???                  0x0000000000d53dc0 0x00d53dc0()
#  5 ???                  0x0000000076e8e662 0x76e8e662()
#  6 ???                  0x00000000772a4d07 0x772a4d07()
#  7 ???                  0x00000000772675c4 0x772675c4()

If on linux, libtorrent-rasterbar and Qt version

N/A

What is the problem

Torrents were in ~1KB download speed for 1+ hours. Once clicking through Tools -> Options. The popup dialog was frozen and 30 seconds later, the crash dialog showed.

What is the expected behavior

No crashing.

Steps to reproduce

One time crash.

Extra info(if any)

N/A

[xavier2k6]

@MewX Unfortunately there's nothing really to go on from that stack trace as it's empty, it doesn't contain any debug symbols etc.

Did you download qBittorrent from an official source or is this a portable version from somewhere like portableapps?

It is advisable that you use the OFFICIAL 64bit version of qBittorrent as you are running a 64bit OS.

[MewX]

@xavier2k6 Yes, I did download it from the official website.

from:

[xavier2k6]

Can you reproduce the crash with the 64-bit version?

[MewX]

@xavier2k6 I couldn't reproduce it even on 32-bit version. I guess it's one-time crash.

So, this issue report might not be helpful at all. However, it might worth making the popup error report more useful in this case instead of producing this sort of empty stack tracing? What do you think?

Please feel free to close this one as I don't think I can reproduce this one, unless you have other instructions for me to retrive logs or so that I can be useful here.

[xavier2k6]

I couldn't reproduce it even on 32-bit version. I guess it's one-time crash.

If it happens again, please report it.

So, this issue report might not be helpful at all. However, it might worth making the popup error report more useful in this case instead of producing this sort of empty stack tracing? What do you think?

We are still not 100% certain on why such empty stack traces occur (usually happens if exe & pdb files are not in same installed directory) It may also be a corrupt debug helper file in OS.

Please feel free to close this one as I don't think I can reproduce this one, unless you have other instructions for me to retrive logs or so that I can be useful here.

Please use the 64-bit version going forward.