-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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 5.0.1 continues to use a lot of memory until crash #21710
Comments
Maybe it's not the new disk IO mode, but a file pool bug: arvidn/libtorrent#7778 The file pool bug caused great increase of memory usage as well. |
Did you do a fair test? Because So if you keep it disabled, then do you have no memory issues with v5.0.1? Did you went back to v4.6.7 built with libtorrent v2.0.11+ or you are actually using with v1.2.19+?
You modified qBittorrent v5.0.1 code to use old Qt version or forgot to recheck that v5 uses Qt 6.7.3 on Windows OS? |
I don't think it has something to do with the disk IO type. |
@qBittUser I'm very sorry but I'm away from home now; I'll do some test as soon as I get home. Anyway... @HanabishiRecca is right...seems that I have exactly the same issue.
But sincerly, also @KevinMX seems to describe the same behavior: Talking about memory issue, for me version 5 and 5.0.10 has the same behavior. When I installed version 5, obviously I hadn't setup anything. |
That issue you and @KevinMX mentioned is about unofficial edition of qBittorrent, many there are not using qBittorrent with the same libtorrent version, don't have same settings, are using extra features or a different OS. So your way to reproduce v5 memory issue, what you mentioned in opening post, is totally different than others there and a fair test needs to be made to find if and then why certain official and unofficial v4.6.7 works fine. |
Yeah, I'm also quite uncertain if the official qB and unofficial qBEE are leaking memory due to the same reason. I've rolled back to 4.6.x due to, well, some of my trackers don't allow 5.x yet. Quite busy recently, will try to find a minimal reproducible config someday. |
Not really, qBittorrent enhanced is using same libtorrent version (1.2.19+git8ad05ebd41) as official. |
Why can't anyone provide good tests??? |
Can confirm same problem. Even with os cache disabled, memory priority low and process priority low with cache set to 4GB max qBittorrent will push memory hard until it is loaded 99%, then makes other stuff crash, and then it swallows that memory too. Currently 51 of 64GB loaded. Update from 5.0.0 to 5.0.1 did not fix it. System unusable with qBittorrent active. |
We don't know how make good test. I have 1000 torrents, and I have the same issue. |
Somebody who can repro the issue could try to make 3 process memory dumps (with a few hours delay between them), and then try to compare memory contents to try to understand what kind of data is leaking. Is the issue reproducible when all the hundreds of torrents are paused/stopped? |
qBittorrent & operating system versions
qBittorrent: 5.0.1 x64
OS: Windows 10 Pro 22h2 19045.5011
Qt: 6.4.3
Libtorrent: 2.0.11.0
What is the problem?
I have about 2000 files, all from 1GB to 80GB. I updated qbittorrent to the latest version (5.0.1). I set the disk IO to "Simple pread/pwrite". But unfortunately as soon as I start qbittorrent, it immediately starts increasing memory usage until it becomes impossible to do anything. At that point qbittorrent crashes or I have to terminate it.
I went back to version 4.6.7 and it works great.
Steps to reproduce
No response
Additional context
No response
Log(s) & preferences file(s)
qBittorrent.json
The text was updated successfully, but these errors were encountered: