Open thiemel opened 1 year ago
I have a similar issue in MacOs Big Sur 11.7.6. 100% CPU consuming with version 3.8.2 and keeps showing "sincronizando" (synchronising)
I'm running the Mac desktop client on MacOS 13.4, with the same version of nextcloud server and similar numbers of files. I am having the same problem as described here since upgrading the client to 3.8.2. I'm willing to provide any additional details if it would be helpful.
Can confirm problems with 3.8.2 on Windows 10 it feels like the desktop client checks any file on every sync process. This takes 30 Minutes for a single sync run in my case.
Same for me. Mac monterey 12.6.6 Nextcloud server 26.0.2 Desktop client 3.8.2 osx-21.6.0
Same for me. Mac monterey 12.6.6 Nextcloud server 26.0.2 Desktop client 3.8.2 osx-21.6.0
And solved by downgrading to 3.8.0. Now it works like a charm. I will wait the next release of client...
I will add that this is also an issue on Linux and I noticed it started last week after running a full system upgrade.
EndeavourOS Kernel: 6.3.4 Nextcloud Server: 26.0.1 Nextcloud client: 3.8.2-1
Update: Rolling back to 3.8.1 has resolved this.
I can confirm the problem in MacOS too. After Upgrade from 3.8.1 to 3.8.2
Same issue here.
Windows: 10 & 11 Nextcloud Server: 26.0.2 Nextcloud Client: 3.8.2
Rolling back to 3.8.1 has resolved this.
Please check and report back if this is fixed by PR https://github.com/nextcloud/desktop/pull/5680 that is intended to fix https://github.com/nextcloud/desktop/issues/4106.
Issue can be closed. Problem seems to be fixed in next official version/update.
@thiemel What version are you talking about and do you have a link to the relevant PR or commit(s) that supposedly fix this? The current status for me is still broken I am unable to confirm any progress towards a fix.
This seems to still be present on client v3.10.0 with server v25 on macOS 10.14
This is with 100+GB sync folder....
It is however not consistent, First updated from 3.7.x it used 100% as was unresponsive for a while, but then settled down. It was then fine so I ignore, but it has now happened again. And after restarting it happens repeatedly.... Didn't happen before update, and I'd avoided v3.8.x & v3.9.x due to 100% usage issue raised above.
Same issue
OS: MacOs 14.0 - Apple M1 Pro Desktop Client: Nextcloud 3.10.1git Server: Nextcloud 27.0.2
Reverted back to 3.8.1. So far the issue is fixed.
Same issue
OS: MacOs 14.0 - Apple M1 Pro Desktop Client: Nextcloud 3.10.1git Server: Nextcloud 27.0.2
Reverted back to 3.8.1. So far the issue is fixed.
Nope.. after letting it sync my ~80GB of data, it started to 100% CPU again.
What other information can I provide to help with this issue?
I have had the same problem since the last server update to 27.1.2, downgrading the client didn't help, nor did a reinstall or other recommended measures. The only thing that really helped is to deactivate the automatic limitation of the download and upload bandwidth in Settings/Network, after which the CPU load (Macmini M1) is at 10 - 20%. However, this leads to other users in the network complaining about a spotty internet connection.
The same problem existed with two other older Macminis (3.6 GHz quad-core Intel Core i3/Sonoma/Client 3.10.1 and 2.6 GHz quad-core Intel Core i7/Catalina/Client 3.9.4) and could be solved in the same way. So it doesn't seem to be the client, but the server.
Further research has provided information about the changed default setting "System config value bulkupload.enabled set to boolean true" on newer server versions. After setting this to "false", the automatic bandwidth limitation workes perfectly again and the CPU load is no longer increased by the clients. This could be a workaround until the problems with the bulk upload are solved.
Just as a point of reference I checked and this bug is still around in v3.11.0, so when I updated the Arch Linux package to that version I left the long-running patch in that disables bulk uploads. Basically it just falsifies the return code from the server when the client asks if it supports bulk uploads so it thinks the server doesn't support it and doesn't try.
This monkey patch has been in place for some time now so don't take anybody saying "it works for me" seriously if they are on Arch Linux!
Also this is not a performance bug! It isn't just slow it absolutely cripples the host computer and fails to run/load into any usable state. It's just a bug, not a performance issue.
⚠️ Before submitting, please verify the following: ⚠️
Bug description
After Windows' Nextcloud client upgrade from 3.8.1 to 3.8.2 it consumes 100 % CPU (1 core). Although it shows "green" icon in the tray, it shows "blue" synchronising when opened. The application is very slow and "unresponsive"
I have ~2200 folders and ~117000 files in them (821 GB in total) saved on my private Nextcloud server version 25.0.6.
Here is 3.8.1 client:
Here is 3.8.2 client:
Previously it had problem with .css~ and .txt~ local files, so I deleted them.
OS: Microsoft Windows 10 - Version 10.0.19045.2965
Steps to reproduce
Install NextCloud client 3.8.2 or higher, start the application.
Expected behavior
After some time since the application starts, the CPU usage by the app should go to "zero".
Which files are affected by this bug
nextcloud.exe
Operating system
Windows
Which version of the operating system you are running.
Windows 10
Package
Appimage
Nextcloud Server version
25.0.6
Nextcloud Desktop Client version
3.8.2
Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 3.4.2 to 3.4.4)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
Are you using an external user-backend?
Nextcloud Server logs
Additional info
Password for both ZIP & 7zip archive is the string after "fileId=1203249&c=" in Server logs above. Why 7-zip in ZIP archive? Because uncompressed logs have ~1GB due to the "bug" in 3.8.2 and GitHub does not allow *.7z files.
nextcloud-3.8.1+3.8.2-debug.7z.zip