Is anyone also experiencing a really slow settings UI on the latest Windows clients ?
I opened a Github issue weeks ago, but it seems mostly abandoned:
My Nextcloud root contains about 50 top-level folders. Since the migration to QT6 on Windows, the settings UI is almost unusable. Listing the folders takes ~10 seconds and thereafter, every single click (like moving the Windows or scrolling down the list) takes 2-3 seconds. During that time, the nextcloud.exe is using 100% CPU. The culprit is the “Qt6Core.dll” thread. Disk remains idle.
I can very easily/reliably reproduce the issue by simply creating ~50 empty top level folders on a test instance.
This happens since version 3.14 on Windows 11 23H2/24H2 using both light and dark themes.
3.13 works like a charm and is my daily driver at this point.
In terms of knowledge to debug the issue, github is the right place to do it. But sure, if you find more people with this problem, this can help to figure out the issues.
Do you have more server requests when you go through this list (e.g. it asks much more then the top-level folders, or too many times)?
Do you have programming environmets installed on your computer, that might include qt as well?
For the moment, I just work on Win10 (if not Linux), so I can’t directly test. But Win11 should be more widespread that if it was a general problem, it would trigger much more reports.
I can only see 4-5 requests when opening the settings UI. Once the folder list is visible, moving the Windows or scrolling down the folder list is slow without generating a single request.
So the UI is locally slow.
I also just realized that if I fold the folder list, then the UI becomes far more responsive. As soon as I unfold the list (and make the ~50 folders visible) then it’s slow again.
I could verify the problem myself and there were answers to your bug report from others confirming the issue. So we cannot do anything here and must hope that the developers fix this issue.
I tried to find this quickly, but that isn’t so easy if you don’t know the code, and you don’t have a development environment, where you can just attach a debugger to check.
Let’s follow the github disscusion and close here: