Skip to content

[BUG] WebUI via HTTP creates a memory leak #414

@rockjob

Description

@rockjob

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Might be related to qbittorrent/qBittorrent#21651
Docker image: lscr.io/linuxserver/qbittorrent:5.1.4-libtorrentv1

When connecting to the web UI via HTTP the browser gives the following error message as a response:
Cookie “SID” has been rejected because a non-HTTPS cookie can’t be set as “secure”.
The request being sent is /api/v2/sync/maindata?rid=1
The RID is not being incremented.

This results in the memory usage slowly increasing until container or system crashes. It doesn't appear to release the memory when you close the browser.
A work around is possible by using HTTPS, however I don't think allowing HTTP connections that result in a memory leak style situation should be allowed.

Expected Behavior

The web UI should be able to run without exhausting the server of memory.

Steps To Reproduce

  1. Connect to web UI via http
  2. Leave web UI running
  3. Watch memory usage increase.

Environment

- OS: Linux pi5 6.12.34+rpt-rpi-2712 #1 SMP PREEMPT Debian 1:6.12.34-1+rpt1~bookworm (2025-06-26) aarch64 GNU/Linux
- How docker service was installed: apt-get install docker

CPU architecture

arm64

Docker creation

services:
 qbittorrent:
    image: lscr.io/linuxserver/qbittorrent:5.1.4-libtorrentv1
    container_name: qbittorrent

Container logs

#Nothing useful ever printed in docker logs. Only shows startup message.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions