Memory leak on Win10, qB 4.4.1 x64

[nightrider77]

qBittorrent & operating system versions

Windows 10 x64 21H2
RAM 32GB DDR-4 3333mhz
qB 4.4.1 x64

What is the problem?

When I download torrents with many seeders, download speed (I will write in megabytes, not megabits) is equal to ~40 MB/s or more (tested on 90 MB/s), qB starts to fill all available RAM. When it finishes download, RAM is being released and drops to 60MB.

Noticable is the amount of Memory Hard Faults per second in a Resource monitor (3 009).

Steps to reproduce

No response

Additional context

No response

Log(s) & preferences file(s)

No response

[NotTsunami]

Duplicate issue. Also not a memory leak, this is the way libtorrent 2.x works. See arvidn/libtorrent#6667 for an explanation. There is an open pull request to limit this, however, and will probably land in 4.5.x.

[nightrider77]

But it is an urgent issue, because PC starts lagging, especially mouse cursor, freezes every few seconds. Apparently, the only solution is to migrate to another client :(

[thewriteway]

workaround resolution raised here - #16456
potential fix here - #16485

[nightrider77]

Can someone tell what is the last stable qB release, which doesn't have libtorrent? Thank you.

[NotTsunami]

Can someone tell what is the last stable qB release, which doesn't have libtorrent? Thank you.

libtorrent is the library that qBittorrent relies on for all of its torrent functionality, so not quite possible on that one. If you want to avoid a version with libtorrent 2.x, you can use 4.3.9.

[NIC3PU]

Can someone tell what is the last stable qB release, which doesn't have libtorrent? Thank you.

libtorrent is the library that qBittorrent relies on for all of its torrent functionality, so not quite possible on that one. If you want to avoid a version with libtorrent 2.x, you can use 4.3.9.

Welp guess i'm rolling back to 4.3.9 again.

[thewriteway]

similar issue of #16166

[nulllee]

same problem，4.4.1 x64 qt6 win10x64 21h2

[ghost]

Fixed by #16617 and #16700 on Windows systems. Will be included in next release(4.4.2).

[nulllee]

Fixed by #16617 and #16700 on Windows systems. Will be included in next release(4.4.2).

thank you.