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
qBittorrent 4.4.3.1 memory leak ? #17095
Comments
Update to 4.4.3 when possible. |
4.4.3 same problem too |
Then you should check "Physical memory (RAM) usage limit" in Advanced Settings because that settings prevents qB from horking up memory. If that not help then recheck all settings because there are settings that potentially could take up a ton of RAM. |
4.4.3 isn't available in the BSD repos yet but I might just try to build from source.... I checked for updates yesterday, 4.4.2_1 was available. Installed and now none of the 10 instances will start. Never had this happen from an update before, but haven't had time to troubleshoot the cause yet... ** Strangest crap. 4.4.2.1 would NOT START. I have 10x instances. They all failed to start after qbit/dependencies were updated, exiting with sig 10 or 11. Qbit logs didn't show anything except that it was loading the fastresumes. Starting with a fresh config, same issues. Built 4.4.3.1 from source. Also, would NOT START. Renamed my BT_backup folder, and all instances started just fine. Shut them all down, copied back the original BT_backup folders, and qbit started fine... As far as memory leak, I will see how this version does. |
Updated with latest info. I fixed a different issue (qbit not starting) by building 4.4.3.1 and libtorrent 2.0.6.0 from source...but the ram usage still seems unusual. |
It's not memory leak it's how libtorrent 2.0.x memory mapped files work. You should read arvidn/libtorrent#6667 |
Memory use from top is low for qbit on 4.4.3.1. Lower than it's been in the past. It's not creeping to extremes as it was before, or getting so bad the paging starts being used. However, the OS sees 58-60gb of RAM in use by services, which doesn't match from what top displays, however didn't start until later versions. This means less ram available for ZFS to use as cache. Whatever the case, the issue when I originally posted this seems to be resolved in newer versions, so will close this. |
qBittorrent & operating system versions
qBittorrent-nox: 4.4.3.1 x64
Operating System: TrueNAS 13.0 (FreeBSD 13.1)
Qt: 5.15.2
libtorrent-rasterbar: 2.0.6.0
What is the problem?
There seems to be a memory leak. Qbit would use up to ~8-10gb ram on past versions but not go beyond that for weeks at a time. On this version (seemed to start with 4.2?), if left to run long enough it will creep up much higher.
I disabled disk cache and enabled to let the OS handle it. The ram usage for non-busy instances is much lower than with disk cache enabled, however the more active instances continue to increase in ram usage. After a restart of qbit, ram usage is 500-1000MB. When left to run long enough, I've seen it go up to 25GB.
Steps to reproduce
Additional context
From Top... In the past it never showed such high numbers from SIZE. The RES amounts are actually lower than in the past...
...yet the overall RAM usage for services (the only "services" I run are qbit) is extremely high after only a few hours:
I saw a similar post for Windows but figured I should do a separate report for a different OS / qbittorrent-nox. In the past, with the same number of qbit services and torrents running, a total of ~20GB ram was used by all services, even after weeks.
Log(s) & preferences file(s)
No response
The text was updated successfully, but these errors were encountered: