In any case, the leak behavior is not changed. If set to -1 or a fixed value like 4096 MB, seeding performance suffers. QBittorrent has the internal disk cache set to 0 (disabled) and is using the OS cache. They both leak in the same manner and qBittorrent crashes when the RAM is exhausted. I also have qBittorrent 4.5.1 LT1.2 QT6 on two Windows 10 boxes. The boxes have Windows 7 圆4 (new install + updates). I'm weary of my workaround and looking at older versions and other clients. My main seedbox has 64GB RAM and 4 qBittorrent instances which exhaust the RAM in about 16 hours. This is a major issue for me as one box only has 8GB RAM, and qBittorrent runs about 8 hours before crashing. I don't close qBittorrent as it'll hang with a zombie qbittorent.exe in Task Manager. I've learned to pause then resume seeding when 90% of RAM is used, which releases the leaked RAM. My qBittorent crashes when the RAM is exhausted. The leak is not counted in the qbittorrent.exe process in Task Manager, but you notice it by available RAM dropping. Said another way: seed 1GB and 1GB of RAM is leaked. I'm seeing a memory leak with qBittorrent 4.5.0 and 4.5.1 LT1.2 QT5 when seeding that appears to be 1:1 with the data being seeded.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |