Crash when checking torrent with piece size of 256.0 MiB

[YouMiNope]

qBittorrent & operating system versions

qBittorrent: 4.6.5 x64
Operating system: Windows 10 22H2

What is the problem?

I have a torrent that contains 3813 files with a total size of 279.43GiB, when checking it consumes all my 16Gb RAM and then crash. I assume there is some algorithm flaw in the checking codes that need to be fixed.

Steps to reproduce

1. check a LARGE size torrent (in my case, 279.43GiB)
2. you wait the memory fill up
3. witness your computer crash

Additional context

My RAM useage:

qbittorrent:

Log(s) & preferences file(s)

No response

[stalkerok]

This is a consequence of incorrect client configuration, also you didn't specify libtorrent version, I suspect it's 2.0.
Also

Log(s) & preferences file(s)

No response

[YouMiNope]

This is a consequence of incorrect client configuration, also you didn't specify libtorrent version, I suspect it's 2.0.

here are my supplementary informations:

crash report

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 10 Version 22H2 10.0.19045 x86_64

Caught signal: SIGABRT

 0# 0x00007FF63F530D13 in qbittorrent
 1# 0x00007FF63F530589 in qbittorrent
 2# 0x00007FF63F52A515 in qbittorrent
 3# 0x00007FF63F820EEA in qbittorrent
 4# 0x00007FF63F8234C8 in qbittorrent
 5# 0x00007FF63F823531 in qbittorrent
 6# 0x00007FF63F818398 in qbittorrent
 7# 0x00007FF63F818FD4 in qbittorrent
 8# 0x00007FF63F819042 in qbittorrent
 9# 0x00007FF63F814F4D in qbittorrent
10# 0x00007FFC7ABB292F in ntdll
11# 0x00007FFC7AB62554 in ntdll
12# 0x00007FFC7AB622A7 in ntdll
13# 0x00007FFC781FBA99 in KERNELBASE
14# 0x00007FF63F815238 in qbittorrent
15# 0x00007FF63F807F2B in qbittorrent
16# 0x00007FF63F8130AD in qbittorrent
17# 0x00007FF63EED66A8 in qbittorrent
18# 0x00007FF63EEDB4A5 in qbittorrent
19# 0x00007FF63EEDB680 in qbittorrent
20# 0x00007FF63EEE1735 in qbittorrent
21# 0x00007FF63EEE1B98 in qbittorrent
22# 0x00007FF63EED8DB5 in qbittorrent
23# 0x00007FF63EED47C5 in qbittorrent
24# 0x00007FF63F8334CA in qbittorrent
25# 0x00007FFC7A427344 in KERNEL32
26# 0x00007FFC7AB5CC91 in ntdll

Log

(N) 2024-06-30T12:44:43 - qBittorrent v4.6.5 started
(N) 2024-06-30T12:44:43 - Using config directory: C:\Users\Administrator\AppData\Roaming\qBittorrent
(N) 2024-06-30T12:44:43 - Trying to listen on the following list of IP addresses: "0.0.0.0:8781,[::]:8781"
(I) 2024-06-30T12:44:43 - Peer ID: "-qB4650-"
(I) 2024-06-30T12:44:43 - HTTP User-Agent: "qBittorrent/4.6.5"
(I) 2024-06-30T12:44:43 - Distributed Hash Table (DHT) support: ON
(I) 2024-06-30T12:44:43 - Local Peer Discovery support: ON
(I) 2024-06-30T12:44:43 - Peer Exchange (PeX) support: ON
(I) 2024-06-30T12:44:43 - Anonymous mode: OFF
(I) 2024-06-30T12:44:43 - Encryption support: ON
(I) 2024-06-30T12:44:43 - UPnP/NAT-PMP support: ON
(I) 2024-06-30T12:44:43 - Successfully listening on IP. IP:XXXXXXXXXXXX. Port: "TCP/XXXX"
......
(N) 2024-06-30T12:44:43 - Restored torrent. Torrent: "the_LARGE_torrent"
(N) 2024-06-30T12:44:59 - Torrent resumed. Torrent: "the_LARGE_torrent"

[glassez]

here are my supplementary informations

It looks like your qBittorrent installation is broken, so it can't produce a useful stack trace.

[YouMiNope]

It looks like your qBittorrent installation is broken, so it can't produce a useful stack trace.

I think it's just some random trace due to out of memory, I tried to reproduce but the crash reporter just crashed itself, and my PC almost crash too.

This is a consequence of incorrect client configuration,

Im curious if there are some qbittorent settings that can get rid of that. How do I get the right configuration?

[xavier2k6]

@YouMiNope any crashdumps in %LOCALAPPDATA%\CrashDumps?

also, run sfc /scannow in an elevated command prompt & that should highlight/take care of any corrupt OS files etc.

[xavier2k6]

Related to #19745

[YouMiNope]

@YouMiNope any crashdumps in %LOCALAPPDATA%\CrashDumps?

also, run sfc /scannow in an elevated command prompt & that should highlight/take care of any corrupt OS files etc.

I found two crashdumps titled qbittorrent.exe that created yesterday when my PC crashed.
CrashDumps.zip

the sfc /scannow says Windows Resource Protection did not find any integrity violations.

[xavier2k6]

unknown exception (0xc0000409)

Dump gives above but no symbols/real info to go on.

E:\Program Files\qBittorrent\

You have qBittorrent installed here, does it have an associated qbittorrent.pdb file in this folder too?

[YouMiNope]

You have qBittorrent installed here, does it have an associated qbittorrent.pdb file in this folder too?

sorry I forgot to mention that I reinstalled my qbittorrent with latest v4.6.5 while the crashdumps were created when I was using v4.6.2, I don't know if the v4.6.5 .pdb will help. that file is too big to upload in github, if you want it I can email it to you.

by the way I tested libtorrent 2.0 built and it works very well.

[xavier2k6]

No need to upload pdp file, just ensure it is next to qbittorrent.exe where qbittorrent is installed.

The issue seems to be only with libtorrent 1.2.x version, It would be most helpful & highly appreciated if you could try to produce a valid stack trace (using libtorrent 1.2.x version) from instructions/method in #20869 (comment)

[YouMiNope]

Seems like I captured a crash. the log file produced by debugdiag as follows:
qbittorrent__PID__16324__Date__06_30_2024__Time_06_09_49PM__611__Log.txt

hope that will help

[scomnoob]

cant confirm that bug
5.0 beta1 on win11
RAM usage is ok on 400gb torrent while checking

[stalkerok]

@YouMiNope Can you share the torrent file or hash (if it's not a private torrent)?