qbittorrent is using an insane amount of memory when checking large torrents and forcing me to frequently check them

[Pryodon]

qBittorrent & operating system versions

qBittorrent: 4.6.5 x64
Qt: 6.4.3
Libtorrent: 1.2.19.0
Boost: 1.85.0
OpenSSL: 1.1.1w
zlib: 1.3.1
Windows 10 Pro x64 Version 22H2 (10.0.19045) OS build 19045.4651
Windows Feature Experience Pack 1000.19060.1000.0

What is the problem?

In the attached .zip file, I included the logs and torrent files I am having issues with. Each of the torrents are about 279 GB in size and contain many files.

See the two attached images. The program is using an extreme amount of memory when checking files. I had to manually create a 300 GB windows memory page file for the file checking to succeed! It appears that the entire 279 GB torrent file is being loaded into memory when it is being checked. When a subsequent torrent file is being checked, that is also loaded into memory causing windows to close qbittorrent because windows has run out of system memory. It only runs out of memory when I am checking the attached torrent files. The rest of my torrent files don't have this issue.

I started qbittorrent. I previously had the torrents downloading or seeding. The program forced me to check all of the torrents. These files are huge so I had to wait a long time for them to be checked. In order to successfully check the files, I pause them then check them one at a time. After I check one torrent, I have to close the program and restart it or else the system runs out of memory and windows closes the program. I start the program again and check the next torrent. Close the program. Restart the program. Check the next torrent. Close the program, etc.

I closed qbittorrent did some other stuff on my computer then I rebooted my computer. When I started up qbittorrent again, it said that all my files had to be rechecked again! This makes no sense to me because they were just checked earlier.

I could not locate a crash report log file but some of the logs have errors or warnings listed in them. Windows closed the program several times because it used up the entire 300 GB memory page file. I had to manually create a huge memory page file for the checking to succeed.

I must close qbittorrent after checking each of those torrents or windows closes it because it uses up all of the memory.

Steps to reproduce

You'll probably have to download at least two of the attached 279 GB torrents to reproduce this error. Each of these torrent files is about 279 GB.

I just started having an issue with the file checking yesterday. I had never had to check these files before then. qbittorrent is forcing me to recheck the files frequently.

Additional context

These two screen captures are of windows task manager showing just how much memory qbittorrent is using. I've got 32 GB RAM plus a 300 GB system memory page file and qbittorrent is using all of it!

Log(s) & preferences file(s)

qbittorrent-errors.zip
qBittorrent.ini.txt

[stalkerok]

Piece size 256mb
Related #19745 #21011
also, perhaps #21042
Maybe we should start closing as duplicates already.

[Pryodon]

Here are two crash dump files I just noticed:
qbittorrent.exe.2168.dmp
qbittorrent.exe.8336.dmp

Any idea as to why qbittorrent is forcing me to recheck all of my torrents frequently? When I close the program, all of my torrents are downloading or seeding. Frequently when I start up the program, it forces me to recheck all of my torrents! It takes forever to check those huge files and as I mentioned, I have to babysit it while it is doing that.

Also, if I didn't make it clear above, when one of those files is checked, it is not unloaded from memory when it is finished being checked. If I don't close the program before the next file is checked, it also tries to load that file into memory while the other file is still in the memory causing windows to run out of memory and close the program. So, after each of those huge files is checked, I have to shut down the program, then start it up again to check the next file. This is very time consuming.

[xavier2k6]

@Pryodon It does appear that you are suffering the same issue as pointed out in #21063 (comment)

However, one of those dumps that you provided (*8336.dmp) shows a stack overflow exception (0xC00000FD)

It would be most helpful & highly appreciated if you could try to produce a valid stack trace from instructions/method in #20869 (comment)