You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Run headless
Open web UI
Have some active downloads
Wait for some time
Additional context
No response
Log(s) & preferences file(s)
No response
The text was updated successfully, but these errors were encountered:
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
Additional context
No response
Log(s) & preferences file(s)
No response
The text was updated successfully, but these errors were encountered: