qbittorrent / qBittorrent

qBittorrent BitTorrent client
https://www.qbittorrent.org
Other
27.44k stars 3.9k forks source link

Crash; Caught signal: SIGABRT and SIGSEGV #21469

Open AthoyeMahmud opened 3 days ago

AthoyeMahmud commented 3 days ago

qBittorrent & operating system versions

qBittorrent version: v5.0.0 (64-bit) Libtorrent version: 1.2.19.0 Qt version: 6.7.3 Boost version: 1.86.0 OpenSSL version: 3.3.2 zlib version: 1.3.1 OS version: Windows 11 Version 22H2 10.0.22621 x86 64

What is the problem?

It crashed the first time unexpectedly, then it crashed again while I was writing this bug report. I couldn't copy it easily so I attached the screenshot in the logs

Steps to reproduce

No response

Additional context

No response

Log(s) & preferences file(s)

image

xavier2k6 commented 3 days ago

@AthoyeMahmud Any reproducible steps? any *.dmp files?

AthoyeMahmud commented 3 days ago

@AthoyeMahmud Any reproducible steps? any *.dmp files?

@xavier2k6 Could you please tell me where I can find the right dump file?

And also I don't know what made this happen so I can't reproduce it.

xavier2k6 commented 3 days ago

%userprofile%\AppData\Local\CrashDumps

AthoyeMahmud commented 3 days ago

Thanks! Here ya go qbittorrent.exe.28640.dmp

xavier2k6 commented 3 days ago

In qbittorrent.exe.28640.dmp the assembly instruction at qbittorrent+7f352d in C:\Program Files\qBittorrent\qbittorrent.exe has caused a stack overflow exception (0xC00000FD) when trying to write to memory location 0x74603ff8 on thread 17

  1. How many torrents do you have loaded?
  2. Can you go through them to see if any have a piece size of 256MiB+?
  3. Were torrents re-checking?
  4. Did you run out of space?
AthoyeMahmud commented 3 days ago

@xavier2k6 > > In qbittorrent.exe.28640.dmp the assembly instruction at qbittorrent+7f352d in C:\Program Files\qBittorrent\qbittorrent.exe has caused a stack overflow exception (0xC00000FD) when trying to write to memory location 0x74603ff8 on thread 17

  1. How many torrents do you have loaded?
  2. Can you go through them to see if any have a piece size of 256MiB+?
  3. Were torrents re-checking?
  4. Did you run out of space?
  1. 117
  2. I just did, piece sizes rarely exceeded 4 MiB, a few 8-16 MiB, and one 32 MiB
  3. Nope
  4. Nope.