Increasing RAM continuously

[Bkk20]

I'm running qBittorrent v5.1.2 WebUI (64-bit) inside a Proxmox LXC container with limited RAM (4GB). Over time, RAM usage grows continuously until the container becomes unresponsive. This happens even with few active torrents or when all torrents are stopped.

• File Pool Size and Disk Cache doenst change anything.
• Container logs show normal operation; the container does not crash immediately but becomes unresponsive as RAM fills.
  Has anyone successfully run qBittorrent in an LXC or low-RAM environment without hitting this memory leak? Are there settings or patches to prevent this on newer versions?

[Max-kfv2k]

If anyone wants to look into this, please let us know so I can double check version numbers and behavior. I've had the same issue with qbittorrent-nox 4.5.2 on raspbian lite 5.7 (bookworm) and currently using qbittorrent-nox 5.0.1-2 on rasbian lite 6.0 (trixie). I'm not sure it is a memory leak as the usage goes back down when pausing torrents.

[qBittUser]

You should try using newer version, because changelog mentions a lot of fixes related to security and memory leaks.

https://www.qbittorrent.org/news

There's also big difference between what libtorrent version and preferences (settings/options) your using.

[qBittUser]

@Max-kfv2k & @Bkk20

Try using latest qBit v5.1.4 with libtorrent v2.0.11+ and open Tools - Options - Advanced and set Disk IO type to be Simple pread/pwrite, click apply and restart client.

• Why `Disk IO type` default isn't `Simple pread/pwrite`? #22836

• qbittorent to use libtorrent 1.2 home-operations/containers#848 (comment)

If still experiencing issues, then recheck if your qBit Advanced options shows File Pool size as default 100 or not. If it's set higher then maybe you have changed it or maybe are still using various outdated or not good old qBit version preferences.

• Change default settings for "file pool size" and "stop tracker timeout" #19171 (comment)

If still prefer using libtorrent v1.2+, then might also need to consider testing if setting disk cache limit, lowering down maximum peer connections, enabling queueing to have less active torrents or limiting transfer speed helps to avoid high RAM usage.

[soredake]

Good news arvidn/libtorrent@fb4a525