qBittorrent consuming nearly all system resources #16344

New issue

Closed

opened 2026-02-22 03:02:19 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-22 03:02:19 -05:00

Owner

Originally created by @adrianjbone on GitHub (Nov 12, 2024).

qBittorrent & operating system versions

qBittorrent: v5.0.0 (64bit)
Operating system: Linux lancaster 6.11.2-amd64 #1 SMP PREEMPT_DYNAMIC Kali 6.11.2-1kali1 (2024-10-15) x86_64 GNU/Linux
Qt: 6.6.2
Libtorrent: 2.0.10.0

What is the problem?

Qbittorrent is consuming all available memory. 4.5GB + 4.6GB reserve memory + 34.8GB virtual memory - according to the output of 'top'. Also consuming 70% of CPU. I do not have root access to see the output of anything in /var/log, but there is this line repeated about 20 times in the output of dmesg

[217717.241685] systemd-journald[527]: Under memory pressure, flushing caches.

Steps to reproduce

To reproduce I opened qBittorrent and didn't touch it. There were 6 torrents seeding, totalling around 30GB in size. I checked how it was going after around 20 minutes and it was consuming resources again as described above

Additional context

Log(s) & preferences file(s)

qbittorrent.log
watched_folders.json
categories.json

Originally created by @adrianjbone on GitHub (Nov 12, 2024). ### qBittorrent & operating system versions qBittorrent: v5.0.0 (64bit) Operating system: Linux lancaster 6.11.2-amd64 #1 SMP PREEMPT_DYNAMIC Kali 6.11.2-1kali1 (2024-10-15) x86_64 GNU/Linux Qt: 6.6.2 Libtorrent: 2.0.10.0 ### What is the problem? Qbittorrent is consuming all available memory. 4.5GB + 4.6GB reserve memory + 34.8GB virtual memory - according to the output of 'top'. Also consuming 70% of CPU. I do not have root access to see the output of anything in /var/log, but there is this line repeated about 20 times in the output of dmesg [217717.241685] systemd-journald[527]: Under memory pressure, flushing caches. ### Steps to reproduce To reproduce I opened qBittorrent and didn't touch it. There were 6 torrents seeding, totalling around 30GB in size. I checked how it was going after around 20 minutes and it was consuming resources again as described above ### Additional context ![Screenshot_20241112_205134](https://github.com/user-attachments/assets/29a876e8-052e-450b-84b2-f4c95d5323d2) ### Log(s) & preferences file(s) [qbittorrent.log](https://github.com/user-attachments/files/17716974/qbittorrent.log) [watched_folders.json](https://github.com/user-attachments/files/17716976/watched_folders.json) [categories.json](https://github.com/user-attachments/files/17716991/categories.json)

deekerman

2026-02-22 03:02:19 -05:00

closed this issue
added the
Duplicate
label

deekerman commented

2026-02-22 03:02:34 -05:00

Author

Owner

@qBittUser commented on GitHub (Nov 18, 2024):

Can you reproduce with newer qBittorrent v5.0.2 even with libtorrent v1.2.19+?

@qBittUser commented on GitHub (Nov 18, 2024): Can you reproduce with newer qBittorrent v5.0.2 even with libtorrent v1.2.19+?

deekerman commented

2026-02-22 03:02:34 -05:00

Author

Owner

@HanabishiRecca commented on GitHub (Nov 18, 2024):

Looks like a duplicate of #21502.

@HanabishiRecca commented on GitHub (Nov 18, 2024): Looks like a duplicate of #21502.

deekerman commented

2026-02-22 03:02:34 -05:00

Author

Owner

@adrianjbone commented on GitHub (Nov 22, 2024):

Its difficult for me to reproduce without root, my apologies. My only device to use has a broken laptop screen and I've lost root with a careless recursive chown command.. external monitor doesnt work early enough in the boot process to see BIOS options to start reinstall. Anyway with this also being a duplicate I'm happy for it to be closed or deleted or whatever is appropriate

@adrianjbone commented on GitHub (Nov 22, 2024): Its difficult for me to reproduce without root, my apologies. My only device to use has a broken laptop screen and I've lost root with a careless recursive chown command.. external monitor doesnt work early enough in the boot process to see BIOS options to start reinstall. Anyway with this also being a duplicate I'm happy for it to be closed or deleted or whatever is appropriate