Memory leak with 4.4.5

[BrodyStone21]

I'm not sure how to debug this issue, or what exactly is causing it. I noticed I had some memory leaks occurring about a month ago. My system's memory usage would slowly increase over several days until eventually reaching 100% and requiring a reboot.

Originally, I thought the issue was caused by either Sonarr or Radarr, since I had recently set them up. About a week ago, I realized qBittorrent is causing the issues, but I'm unsure if it's an issue with my settings, if I have too many torrents seeding, or something else.

If anyone has any idea what could cause this, I would really appreciate some input. I've included my logs and docker-compose configuration below. I've also included all settings I thought would be applicable.

I'm seeding 440 torrents.

version: '3'

networks:
  vpn_net:
    name: vpn_net
    external: true

services:
  vpn:
    container_name: vpn
    restart: unless-stopped
    image: linuxserver/wireguard
    cap_add:
      - NET_ADMIN
      - SYS_MODULE
    sysctls:
      - net.ipv4.conf.all.src_valid_mark=1
      - net.ipv6.conf.all.disable_ipv6=1
    ports:
      - 51820:51820/udp
      - 6595:6595
      - 6767:6767
      - 6789:6789
      - 7878:7878
      - 8075:8075
      - 8989:8989
      - 9696:9696
    environment:
      - PUID=1000
      - PGID=1000
      - INTERNAL_SUBNET=10.15.15.0
      - TZ=America/Indianapolis
    volumes:
      - /home/ubuntu/.config/wireguard:/config
      - /lib/modules:/lib/modules
    networks:
      vpn_net:
        ipv4_address: 172.18.0.2
  qbittorrent:
    container_name: qbittorrent
    restart: unless-stopped
    image: linuxserver/qbittorrent
    sysctls:
      - net.ipv6.conf.all.disable_ipv6=1
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/Indianapolis
      - WEBUI_PORT=8075
    volumes:
      - /home/ubuntu/.config/qbittorrent:/config
      - /mnt/WD_White/Media:/data
    network_mode: service:vpn
    depends_on:
      - vpn

[custom-init] No custom services found, skipping...
[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
-------------------------------------

[custom-init] No custom files found, skipping...

******** Information ********
To control qBittorrent, access the WebUI at: http://localhost:8075
[ls.io-init] done.

Output of htop --sort=PERCENT_MEM. Note, these numbers will slowly climb over time.

[github-actions]

Thanks for opening your first issue here! Be sure to follow the bug or feature issue templates!

[j0nnymoe]

This is likely due to this version of qbittorrent being based on libtorrent2. Not much can be done unless the package we use gets rebuild on v1.

[BrodyStone21]

This is likely due to this version of qbittorrent being based on libtorrent2. Not much can be done unless the package we use gets rebuild on v1.

Do you know if whoever develops libtorrent2 has been made aware of this issue? Are they planning to develop a fix?

[EsEnZeT]

arvidn/libtorrent#6667

[BrodyStone21]

This is likely due to this version of qbittorrent being based on libtorrent2. Not much can be done unless the package we use gets rebuild on v1.

On August 29, 2022 qBittorrent released an update allowing users to choose between using libtorrent-1.2.x or libtorrent-2.0.x because the user base was complaining of issues.

qBittorrent v4.4.5 was released.
NOTE: The default builds for all OSs switched to libtorrent 1.2.x (RC_1_2) from 2.0.x (RC_2_0). Builds for libtorrent 2.0.x are also offered and are tagged with RC_2_0. The switch happened due to user demand and perceived performance issues. If until now you didn't experience any performance issue then go ahead and use the RC_2_0 builds.
MACOS: The macOS version is not well supported, because we don't have active macOS developers/contributors. The project is in need of macOS developers. If you are a macOS developer willing to help, just go to our bug tracker for a list of macOS related issues. Or try to fix bugs that you yourself have discovered and annoy you.

Can't the developers of linuxserver/docker-qbittorrent just switch which build of qBittorrent they're using? Is there a way we can do this manually? Sorry if I'm answering questions you don't know the answer to, but I'm desperate to fix this.

[BrodyStone21]

Closing this issue as it's not a problem with linuxserver, but how the configuration is being pulled from Alpine.

I've created an issue report requesting Alpine downgrades libtorrent-2.0.x, back to libtorrent-1.2.x.

Please feel free to chime in. I don't have much programming/developement experience, and someone who knows what they're talking about would be very helpful.

[BrainBug80]

Hey Brody,

do you fixed the Memory Problem? I ve got the same problem, and no idea How to...

After Start and stop the docker Container all is okay . and round about 2-3 days the dame ram problem.

Greets
BrainBug80

[fraee]

removed copyrighted filenames.

My problem is Out of memory. I am not sure if it is the same problem. It can be solved after restarting, but it will be the same error one day later.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[BrodyStone21]

Hey Brody,

do you fixed the Memory Problem? I ve got the same problem, and no idea How to...

After Start and stop the docker Container all is okay . and round about 2-3 days the dame ram problem.

Greets
BrainBug80

Having Alpine switch which version of libtorrent is being used fixed the issue for me. Please check out this link for more information.

https://gitlab.alpinelinux.org/alpine/aports/-/issues/14267