starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

Memory leak of webui #17494

New issue

Open

opened 2026-02-22 03:51:56 -05:00 by deekerman · 6 comments

deekerman commented

2026-02-22 03:51:56 -05:00

Owner

Originally created by @katyurua on GitHub (Feb 2, 2026).

qBittorrent & operating system versions

OS: Windows 10 x64 22H2

What is the problem?

When open webui and leave it in browser, memory keeps increasing until all memory is exhausted , then crash.

Steps to reproduce

Run 2 qBittorrent instances on Windows 10, portable mode, different port.
open both webui from another computer, and leave it in browser, do not close it.(chrome/edge)
The memory usage continuously increases every few seconds, from hundreds MB to 50GB+.

Eventually it exceeds available memory, causing system instability and crash.

Additional context

I thought it was a cache issue, then I did a lot of test
turns out it is webui issue

it maybe a problem with cookie or SID, i

Now I use nginx or caddy reverse proxy to avoid this,
access webui with different domain(qb1.lan qb2.lan)
24 hours testing, no memory leak，1G max memory usage,
but this problem is still there.

Log(s) & preferences file(s)

qBittorrent.ini

Originally created by @katyurua on GitHub (Feb 2, 2026). ### qBittorrent & operating system versions OS: Windows 10 x64 22H2 <html> <body>  Qt: | 6.9.3 -- | -- Libtorrent: | 1.2.20.0 Boost: | 1.86.0 OpenSSL: | 3.6.0 zlib: | 1.3.1  </body> </html> ### What is the problem? When open webui and leave it in browser, memory keeps increasing until all memory is exhausted , then crash. ### Steps to reproduce Run 2 qBittorrent instances on Windows 10, portable mode, different port. open both webui from another computer, and leave it in browser, do not close it.(chrome/edge) The memory usage continuously increases every few seconds, from hundreds MB to 50GB+. Eventually it exceeds available memory, causing system instability and crash. ### Additional context I thought it was a cache issue, then I did a lot of test turns out it is webui issue it maybe a problem with cookie or SID, i Now I use nginx or caddy reverse proxy to avoid this, access webui with different domain(qb1.lan qb2.lan) 24 hours testing, no memory leak，1G max memory usage, but this problem is still there. ### Log(s) & preferences file(s) qBittorrent.ini

deekerman added the

WebUI

label

2026-02-22 03:51:56 -05:00

deekerman commented

2026-02-22 03:52:01 -05:00

Author

Owner

@Bambus3000 commented on GitHub (Feb 2, 2026):

I had the same a while back, though I run my qbittorrent on Truenas Scale if that makes any difference.
The solution was quite simple really, a complete reload of the tab by hitting CTRL+F5, or by clearing cookies and site data, I can't remember which one I used. No issues since.

@Bambus3000 commented on GitHub (Feb 2, 2026): I had the same a while back, though I run my qbittorrent on Truenas Scale if that makes any difference. The solution was quite simple really, a complete reload of the tab by hitting CTRL+F5, or by clearing cookies and site data, I can't remember which one I used. No issues since.

deekerman commented

2026-02-22 03:52:01 -05:00

Author

Owner

@kapsh commented on GitHub (Feb 4, 2026):

Reproduces for me on 5.1.4.
I left qbittorrent in background tab for a full day with "Active torrents" filter (about 10 items seeding). Memory used raised from 150-180 MB for fresh page to 2 GB as shown in Firefox's Process Manager. The same amount of total system memory was freed when page was closed, which confirms the number indirectly. Unfortunatelly, devtools profiler reports only 14 MB for javascript objects, so nothing useful to collect from it.

@kapsh commented on GitHub (Feb 4, 2026): Reproduces for me on 5.1.4. I left qbittorrent in background tab for a full day with "Active torrents" filter (about 10 items seeding). Memory used raised from 150-180 MB for fresh page to 2 GB as shown in Firefox's Process Manager. The same amount of total system memory was freed when page was closed, which confirms the number indirectly. Unfortunatelly, devtools profiler reports only 14 MB for javascript objects, so nothing useful to collect from it.

deekerman commented

2026-02-22 03:52:01 -05:00

Author

Owner

@mario-g98 commented on GitHub (Feb 6, 2026):

I have been having this problem for months. If you leave the web UI open, the memory keeps growing indefinitely, until the system freezes and needs to be restarted. I tried many different settings, but nothing helped, so I just gave up. Now I only open the web UI for a short time and then close it. There are a couple of similar issues that are closed, claiming the problem has been fixed, but either it was a different problem or it wasn’t fixed at all.

@mario-g98 commented on GitHub (Feb 6, 2026): I have been having this problem for months. If you leave the web UI open, the memory keeps growing indefinitely, until the system freezes and needs to be restarted. I tried many different settings, but nothing helped, so I just gave up. Now I only open the web UI for a short time and then close it. There are a couple of similar issues that are closed, claiming the problem has been fixed, but either it was a different problem or it wasn’t fixed at all.

deekerman commented

2026-02-22 03:52:01 -05:00

Author

Owner

@Piccirello commented on GitHub (Feb 6, 2026):

This was fixed in https://github.com/qbittorrent/qBittorrent/pull/23228 and will be included in v5.2. In the mean time, try setting a unique session cookie name for each qBittorrent instance.

@Piccirello commented on GitHub (Feb 6, 2026): This was fixed in https://github.com/qbittorrent/qBittorrent/pull/23228 and will be included in v5.2. In the mean time, try setting a unique session cookie name for each qBittorrent instance.

deekerman commented

2026-02-22 03:52:01 -05:00

Author

Owner

@katyurua commented on GitHub (Feb 13, 2026):

This was fixed in https://github.com/qbittorrent/qBittorrent/pull/23228 and will be included in v5.2. In the mean time, try setting a unique session cookie name for each qBittorrent instance.

thanks

@katyurua commented on GitHub (Feb 13, 2026): > This was fixed in https://github.com/qbittorrent/qBittorrent/pull/23228 and will be included in v5.2. In the mean time, try setting a unique session cookie name for each qBittorrent instance. thanks

deekerman commented

2026-02-22 03:52:01 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Feb 14, 2026):

@katyurua qBittorrent beta 1 can be obtained from https://www.qbittorrent.org/download

@xavier2k6 commented on GitHub (Feb 14, 2026): @katyurua qBittorrent beta 1 can be obtained from https://www.qbittorrent.org/download