mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
qBITTORRENT CONSUMES AN INCREDIBLE AMOUNT OF RAM¡¡¡ #5950
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#5950
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @stn666stn on GitHub (Aug 19, 2017).
Please provide the following information
qBittorrent version and Operating System:
qBITORRENT V3.4beta 64bits, Windows 10Pro 64bits
If on linux, libtorrent and Qt version:
What is the problem:
Seeding only one file i´ve noticed qbittorrent is wasting 334,8Mb of ram¡,,,this cannot be true¡¡¡
What is the expected behavior:
qbittorrent neccessarily has to use lots of less RAM, stable version don´t uses more than 30-50Mb¡
Steps to reproduce:
nothing, only opening qb and going to task administrator you see, at this moment, 335,1Mb wasted by qt.
Extra info(if any):
@thalieht commented on GitHub (Aug 19, 2017):
Should be fixed by #7297
@stn666stn commented on GitHub (Aug 19, 2017):
Exactly at this moment QB is using.....811,1Mb of RAM¡¡¡
@stn666stn commented on GitHub (Aug 19, 2017):
i know this is a beta versión...but 811Mb of ram???? is there any momentarily solution?
@ghost commented on GitHub (Aug 19, 2017):
Under Options > Advanced >libtorrent section
Set the value of Disk write cache size to something you feel comfortable with.
15MiB let qBittorrent shrink to around 90MB RAM-usage for me, careless of how many torrents I had loaded into qBittorrent.
@stn666stn commented on GitHub (Aug 19, 2017):
Thanks for the help Thalieht. I left the value of disk cache set at 10Mb (auto-mode appears not working properly) using qb now about 90Mb at this moment.
Maybe some option of my qb settings did a bad job ...
I´m using: integrated tracker with it´s port open, added a list of trackers and limits connections using "azureus upload calculator....and ip filter from emulesecurity...
Another question.....i´m not able to créate an account in qbforums with that ridiculous and confusing captcha.
I´d like leave a commnet about the new icons cause some of them still have the older style, but
I don´t know what have to put in the second blank space.....please help....
@thalieht commented on GitHub (Aug 20, 2017):
You have to answer the question. I'm not sure if it's always the same question but i always get "what's the name of the project (all small letters)" i.e. "qbittorrent"
@stn666stn commented on GitHub (Aug 20, 2017):
Thnks again, mate. I alreasdy did it...system changed second question..."three times seven in numbers"...hahaha
@sledgehammer999 commented on GitHub (Aug 21, 2017):
This is already fixed.
Also this is the first time that "auto" started working as it should. Up until now we used libtorrent 1.0.x series. v3.4.0 switched to the 1.1.x series. Normally under auto mode libtorrent would use 1/8 of system RAM. But the 1.0.x had a bug and it actually disabled the cache instead of telling to use 1/8 of system RAM. Now the new default for the cache is to disable it. Thus mimicking the same behavior as before. Users will still be able to manually choose "auto" which in this case will start using 1/8 of system RAM.
@stn666stn commented on GitHub (Aug 21, 2017):
Thank you, sledgehammer999