[BUG] Very high memory usag 5.0.3

[altendorfme]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I recently installed Bezel and noticed a very high memory usage by qBittorrent in version 5.0.3:

Expected Behavior

No response

Steps To Reproduce

1. Run!

Environment

- OS: Debian 12

CPU architecture

x86-64

Docker creation

services:
  qbittorrent:
    container_name: qbittorrent
    image: ghcr.io/linuxserver/qbittorrent:latest
    ports:
      - 8085:8085
      - 6881:6881
      - 6881:6881/udp
    environment:
      - PUID=1000
      - PGID=1000
      - WEBUI_PORT=8085
    restart: always
    volumes:
      - /opt/qbittorrent:/config
      - /mnt/storage:/storage

Container logs

******** Information ********
To control qBittorrent, access the WebUI at: http://localhost:8085
Connection to localhost (::1) 8085 port [tcp/*] succeeded!
[ls.io-init] done.
Catching signal: SIGTERM
Exiting cleanly
[migrations] started
[migrations] no migrations found
usermod: no changes
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1000
User GID:    1000
───────────────────────────────────────
Linuxserver.io version: 5.0.3-r0-ls371
Build-date: 2025-01-01T22:48:48+00:00
───────────────────────────────────────

[custom-init] No custom files found, skipping...
WebUI will be started shortly after internal preparations. Please wait...

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[eduardlleshi]

I'm seeing the same thing. Memory jumped from ~30MB to 4GB. After a restart, it went back to 30ish MB. Now, it's rising again to the GBs. Not sure if it's a bug with latest release as I did not have any memory stats before.

[j0nnymoe]

You need to check if it's the actual qbittorrent process. Showing the container usage includes all processes within the container.

Also any sort of high memory usage is specific to qbittorrent and it's configured (or because of libtorrent2) and not the container.

[altendorfme]

even in version 5.0.2, this problem continues, in the top I have this information:

[j0nnymoe]

As I mentioned in my previous comment, this isn't going to be container related. To be frank, memory usage in a torrent client is a massive variable as it depends on so many factors with what configuration you're running Vs how many torrents you have.

There just isn't a "oh disable this" I can say which will fix this.

[eduardlleshi]

My qBittorrent rarely has any torrents. 2-3 downloads a week.

Seems like the memory was freed by itself eventually today. Looking and it's history it did download a file before the memory started increasing, and based on some readings that's normal behavior.

@altendorfme Maybe we are overreacting because we're just noticing the memory with the new Beszel tool. I installed it yesterday and that's when I noticed it.

[altendorfme]

@eduardlleshi I've had Beszel for a while now and this problem started for me on day 1

I tested now version 5.0.1 and it seems more stable in this first hour:

There is a big thread about this at qbittorrent/qBittorrent#21502 :/

[altendorfme]

5.0.1 also had problems, I did a rollback to 4.6.7 and it was resolved, I will follow the qbittorrent releases.

[nicolajkl]

I opened an issue over at the actual qbittorrent github and got an answer.
This is due to libtorrent 2.0 using memory mapped files.
Solution: set I/O mode to "simple pread/pwrite" in the advanced tab.

qbittorrent/qBittorrent#22099

[altendorfme]

I opened an issue over at the actual qbittorrent github and got an answer. This is due to libtorrent 2.0 using memory mapped files. Solution: set I/O mode to "simple pread/pwrite" in the advanced tab.

qbittorrent/qBittorrent#22099

This seems to have worked really well!