Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Web UI memory leak in browser #20735

Open
SvbZ3r0 opened this issue Apr 20, 2024 · 0 comments
Open

Web UI memory leak in browser #20735

SvbZ3r0 opened this issue Apr 20, 2024 · 0 comments
Labels
Performance WebUI WebUI-related issues/changes

Comments

@SvbZ3r0
Copy link

SvbZ3r0 commented Apr 20, 2024

qBittorrent & operating system versions

qBittorrent: 4.6.4
Operating system: Unraid, Docker
Docker Image: lscr.io/linuxserver/qbittorrent
Qt: ?
libtorrent-rasterbar: ?

What is the problem?

The qbittorrent web UI has a memory leak, causing open qbittorrent webpages in Chrome to slowly build up in memory until it hits 5.00GB when Chrome force closes the tab with a "Aw.. snap! Something went wrong" error message. Closing the webpage and reopening it resets the memory consumption but causes no adverse effects on performance. The speed of the memory build up is (as far as I can tell) proportional to the number of active downloads.
To be clear, there is no issue on the server end of things. This is a problem found in the client web browser. I have also tested with Edge, but not with any non Chromium browsers.

Steps to reproduce

  1. Run headless
  2. Open web UI
  3. Have some active downloads
  4. Wait for some time

Additional context

No response

Log(s) & preferences file(s)

No response

@xavier2k6 xavier2k6 added Performance WebUI WebUI-related issues/changes labels Apr 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Performance WebUI WebUI-related issues/changes
Projects
None yet
Development

No branches or pull requests

2 participants