qBittorrent
qBittorrent copied to clipboard
qBittorrent 5.0.0 UI has noticeable lag, even for simple actions
qBittorrent & operating system versions
qBittorrent: 5.0.0 x64 Operating system: Windows 11 Pro x64 (23H2), OS Build 22631.4317, Experience Pack 1000.22700.1041.0 Qt: 6.7.3 Libtorrent: 1.2.19.0
Computer specs: Intel Core i5-10400f CPU, Nvidia GTX 1070 GPU, m.2 SSD OS drive where Qbittorrent is installed, 32 GB of DDR4 RAM
What is the problem?
Have tried both 5.0.0 QT6 LT2 and "normal" 5.0.0, same issue with both. Updating RSS feed, selecting a specific torrent in the list, trying to rename an individual file... most actions are noticeably laggy and take a few seconds for something that was barely a noticeable fraction of a second in 4.6.7 QT6 LT2.
Downgraded back to 4.6.7 QT6 LT2, problem immediately gone.
Steps to reproduce
- Have 5.0.0 installed, either version.
- Do most basic UI actions.
Additional context
No response
Log(s) & preferences file(s)
qbittorrent - Copy.log qBittorrent - Copy.txt <--- renamed "Qbittorrent.ini" file
Can you reproduce with default theme instead of using the outdated custom theme file?
Can you reproduce with default theme instead of using the outdated custom theme file?
Just removed the custom theme. Still happening on the default dark theme of 5.0.0.
I am having the same issue on the same version (5.0.0 x64, Qt 6.7.3, Windows 11 Pro x64 (23H2)) on the default dark-mode theme.
I have quite a high-spec system (i7-13700K, 64GB 5600 RAM, RTX4070Ti, etc, etc.) and even moving the window can create EXTREME lag (Jumping the CPU usage of the qBittorrent process from 2% up to almost 12% on a 12-core CPU).
im having similiar lagging issues.
after spending an hour getting my plugins to work again, reinstalling uninstall multiple times yada yada...
it lags when i add a torrent from search, it lags when i update rss. my cpu fans spin up and the qbtorrent.exe start using crazy high cpu freezes and somtimes returns, but cpu stays high until restart. the downlower graph and stats froze, wasnt sure it was had to restart. im spending more time restarting than doing anything else at this point. it freezes so often, i dont even know when or why... ill be going back to v4
qB v5.0.0 Win 11 Qt: 6.7.3 Libtorrent: 2.0.11.0 Boost: 1.86.0 OpenSSL: 3.3.2 zlib: 1.3.1 I can Confirm that now and then my fans speed up and the mouse gets laggy "delayed in movements" I am NOT using any of the "bling bling" without RSS etc.
However i relay heavy on USB-drives and running on a 4k-screen in native Darkmode Using PROTON VPN with WireGuard have not yet tested with LT 1.???
@LazyPajen
Use LT 1.2.19+ if you need to use any kind of external USB or network drives, otherwise you'll need to research and experiment with various settings to partially avoid issues from happening so often, still currently libtorrent v2.0+ will not be so quick and efficient in most use cases.
Let's wait for v5.0.1 to be released, unless someone figures out a good way to find the real reason beforehand why v4.6.7 works fine and v5.0.0 doesn't.
Also better to keep discussions only about the usage of Windows OS and qBittorrent with libtorrent v1.2+ and share if using latest default settings or not, otherwise it's too confusing to figure out what could be causing issues.
qBittorrent 5.0.0 UI has noticeable lag, even for simple actions... not responding!!!
I'm fairly sure the root cause is a code change that caused the performance to scale extremely bad with respect to the number of entries in the torrent list. I've observed this same behavior with 500+ torrents - cleaned house, and now it all turns on a dime.
Try reducing the number of torrents you have to a more conservative amount as a workaround until a real fix is implemented.
The "devs'" released this "stable" update before it was ready! They didn't do them or the software (that WAS a very nice package) any favors, and makes me wonder why they rushed an update that clearly wasn't ready for release to be released?
I'm fairly sure the root cause is a code change that caused the performance to scale extremely bad with respect to the number of entries in the torrent list.
Yes, yes... tell @stalkerok about it, otherwise he doesn't seem to notice this problem with his several thousand torrents.
The "devs'" released this "stable" update before it was ready!
It was "ready" for all those who used intermediate versions all the time while it was being developed. We don't have a team of testers "on the payroll". This is a community based project. The community do this job (all the jobs). Therefore, people like you who sit on the sidelines always get your share of problems after the release of the "stable" version.
Seems majority of users experiencing this "lag" are using Windows 11
Seems majority of users experiencing this "lag" are using Windows 11
I upgraded from 4.6.4 to 5.0.0 on Windows 10 64bit (22H2) and had the same issues with the UI lagging. Switched back to v4.6.4.
i'm also experiencing this unbearable lag. my specs are kinda high end: intel core i5 11600k, nvidia geforce rtx 3050, 32gb ram (task manager shows qbittorrent using a colossal amount of ram when it's lagging) and yes, i do have a long list of torrents so i guess it's linked to that (and yeah i'm using windows 11)
I didn't think 200 torrents was THAT high...
Would someone mind to provide screencast of such lag?
Seems majority of users experiencing this "lag" are using Windows 11
It's actually a good idea to find something that unites all the affected users. IMO, it's hardly Windows 11's fault. Many people here have mentioned that they have "dark mode" enabled. Is there anyone who doesn't have "dark mode" enabled but is experiencing this problem anyway?
Is there anyone who doesn't have "dark mode" enabled but is experiencing this problem anyway?
Me, for example, I'm on Windows 11, qbittorrent 5.0.0 mostly lags 1–3 minutes after startup or after waking pc from sleep.
Yes, yes... tell @stalkerok about it, otherwise he doesn't seem to notice this problem with his several thousand torrents.
@glassez I don't know who that person is, and I don't know why you'd think I do, or why you decided that putting on an attitude is the best possible course of action to take. You're fostering a style of conversation I have a hunch you'd normally say you feel the most sick of. I should probably add that even if you don't feel sick of it, I most certainly do. Please kindly drop this act.
I shared my findings in the best faith possible. Accidentally causing space-time complexity issues and not noticing them is extremely common, and I had every reason to be confident that this is what's happening, as I've observed very direct correlation between me having 500+ torrents in my torrent list and the application seizing up all the time, then wiping it nearly clean and everything becoming normal again.
Evidently this goes against your (or @stalkerok's?) testing, but clearly so does everyone else's experience in this thread. So it'd be informative to know if my (potentially incorrect!) advice of wiping most of the torrent list helps anyone who does experience this issue. It is not helpful or informative to be condescending towards me for reporting on my experience regarding this issue.
So it'd be informative to know if my (potentially incorrect!) advice of wiping most of the torrent list helps anyone who does experience this issue.
No.
Evidently this goes against your (or @stalkerok's?) testing
https://github.com/qbittorrent/qBittorrent/issues/21502#issuecomment-2400516972
but clearly so does everyone else's experience in this thread.
Everyone complains, but no one can say anything concrete. That's the problem.
No.
I was not voicing an opinion there.
Everyone complains, but no one can say anything concrete. That's the problem.
There are several concrete pieces of information in this thread. Your problem seems to be that people haven't identified the exact bug for you on your behalf rather. Acting antisocial after talking about how open source should be a community (thus, social) effort is also quite the problem, but hey, maybe you'll just say a "No." to that one too.
I hope being flippant will help you guys rectify the issue.
Can't solve an issue without knowing what the issue is.
@dio-gh
Deleting transfers is bad advice, it's not good for community and doesn't help to always reproduce or find the exact lag reason.
Better to stick with old v4.6.7 to confirm that it works fine or help out by testing latest development nightly builds or try out resetting settings and using portable mode instead if anything more trastic.
So far only one user has given copy of used settings. So no clue if anyone has unsuitable settings or not. Also if others could atleast share how many active and total torrents, what bandwidth, what hard drives are used and what exact OS version and a screen recording of the lag and Task Manager could atleast help a littlemore if unwilling to try or share anything else.
https://github.com/qbittorrent/qBittorrent/issues/21595#issue-2583234336 still remnants of Qt5 in files.
@MultiKoopa
Open your settings file with Notepad or some other text reader, it has old leftover settings that are not fully compatible or supported anymore and might cause issues.
Your preference file has Qt5 written and unfortunately qBittorrent currently doesn't delete these or replace with Qt6 only and keeps old Qt5 and new Qt6 related ones separately. So you used to have some very old qBittorrent installed that used to be built with Qt5 as default.
So you could try saving down your settings, then exiting qBittorrent, disconnect internet as precaution to avoid unexpected IP leak, open qBittorrent installation location, create New Folder named Profile, open qBittorrent, set most important settings as your previous settings as you had before in the GUI if don't want to use defaults, then exit qBittorrent and compare your old and new settings files to know what lines to delete or not. New temporary portable mode settings are saved inside the Profile folder. Now if you delete, rename or move that portable mode Profile folder and open qBittorrent again then your old settings from default AppData and all transfers are restored as before.
Portable mode was mentioned in the Wiki: https://github.com/qbittorrent/qBittorrent/wiki/How-to-use-portable-mode
Default settings file location also in the Wiki: https://github.com/qbittorrent/qBittorrent/wiki/Frequently-Asked-Questions#user-content-Where_does_qBittorrent_save_its_settings
You're fostering a style of conversation I have a hunch you'd normally say you feel the most sick of.
I'm sorry if I've wronged you. Perhaps I mistakenly took your comment in the wrong context.
There are several concrete pieces of information in this thread.
Maybe I didn't notice some useful information. Could you quote the ones that could help to solve it in your opinion?
Just to add another data point, I'm experiencing extreme lag in the web UI with default theme running on Linux. It may be totally unrelated, but maybe not - the root cause may be the same. With 500 or so torrents, each call to /api/v2/sync/maindata is returning about 1 million characters, or about the same number of bytes / 1MB. Compressed that's about 132kB over the line. This payload is returned regardless of what the UI is showing - i.e. if I'm filtered to one torrent, I still get the entire payload. Maybe that's a reasonable design choice, I don't know the underlying system well enough to say. But I don't think that's the primary issue.
When all my torrents are showing, each time this data is parsed, there's a period of about 1 second that the UI takes to "redraw" the 1MB payload (notably, UI is blocked during this time). 90% of this time is spent in dynamicTable.js#updateRow. When I filter down to a single torrent, the time taken to "redraw" is unnoticeable. Confirmed that prior to 5.0.0, this issue did not exist.
A refresh rate of 1 second in advanced settings makes the web UI basically unusable. I have it set to 5 seconds now and it's okay but not a real fix.
Firefox 131.0.3 (64-bit)
Qt: | 6.7.3 Libtorrent: | 1.2.19.0 Boost: | 1.86.0 OpenSSL: | 3.3.2 zlib: | 1.3.1.zlib-ng
@tayl Could you open separate Issue?
In my case, I'm using it as a Docker container on my NAS.
When I bring up the web UI on my desktop, the PC becomes slow.
The mouse cursor moves slowly or jumps around the screen, the UI doesn't respond to clicks, and the CPU usage jumps up a bit.
So it's something in the web-based UI. The NAS is unaffected.
In my case, I'm using it as a Docker container on my NAS.
When I bring up the web UI on my desktop, the PC becomes slow.
The mouse cursor moves slowly or jumps around the screen, the UI doesn't respond to clicks, and the CPU usage jumps up a bit.
So it's something in the web-based UI. The NAS is unaffected.
ok there's a separate issue for this
I don't use the web UI
it's possible the two issues are connected somehow, but they are different