Nextcloud 2.5.2 client for MacOS uses permanent high cpu load (> 95%) and never stops syncing.
Should not use much CPU capacity. have periods where client does not need to sync
Is permanently syncing & consumes more than 95% cpu load
Client version: 2.5.2
Operating system: MacOS 10.14.5
OS language: German
Installation path of client:
NC 15.0.7
Operating system: Ubuntu 18.04
Web server: Nginx
Database: Mysql 5.7.23
PHP version: php-fpm 7.0
Nextcloud version: 15.0.7
Storage backend (external storage):
Does it actually sync? Some people (including me) are experiencing https://github.com/nextcloud/desktop/issues/1133 in linux
@ja573 on mac macbook I switched back to version 2.3.3 which is working fine. On my iMac I use the 5.2 version and it works but this is a very potent machine with 32 GB RAM. I think the process for sync in the 5.x version consumes to much energy to work fine on notebooks
Thanks @solick - I switched back to 2.5.0, but it's true that it's too heavy, I'll give 2.3.3 a try. I'd expect more people complaining about this.
I am having the same issue with 2.5.2 on the Mac. I am syncing 43G and approximately 96,000 files. It would take multiple days to complete a sync and at the end of it the Mac OS would report the Nexcloud client is not responding. I switched back to 2.3.3 and the sync completed with in a couple hours. I am only syncing a subset of the files from nextcloud my user account on the server has 162G and 478,000 files.
Its strange, sometimes it is working and sometimes it takes hours and days. I have two next clouds in the client managed and from time to time the one is completely blocking the client preventing the other NC to sync. I was wandering if there is a cyclic complete rescan and if it is possible to disable this?
Well I guess that's needed for consistency - the question is why is it faster in previous versions :thinking:
So i gave up and rolled back to 2.3.3
Have a 2 days sync behind me and still seeing high cpu load and sync activities and also non responding of the client over hours!
I'm having the same issue on 2.6.0 after just upgrading from 2.3.3. I start the client and CPU usage goes to 100% and becomes non-responsive. It seems like it does eventually become responsive again, but while it's syncing I can't have any interaction with the client at all; is the client not threaded at all?
Hey,
we've just released 2.6.1 RC1 which is built with Qt 5.12.5 on all platforms (also has OpenSSL 1.1.1d, so it features TLS 1.3).
You may give it a try:
https://github.com/nextcloud/desktop/releases/tag/v2.6.1-rc1
Perhaps it solves the issue due to the Qt upgrade or other fixes?
Similar issue here perhaps? On 2.6.1stable (20191105) CPU is jumping all the time from 0 to 25-47% literally every second, meaning unusable on MacBook whilst on battery power at all. Any remedy?
Only 1 server/sync account configured, & it's a clean fresh empty instance of Nextcloud - with no files except the default ones!
Pausing sync dropped it but still jumping from 0 to 0.5 - why? there shouldn't be any regular (every 1s) process happening when sync is paused? Having to quit it for now. Also, pausing sync manually really shouldn't be the everyday process
I've just updated to 2.6.1 on my ageing Macbook Pro and it is chewing up CPU and energy. The previous version that I had installed (2.5.x?) seemed to run fine, but it's not sensible for me to keep this running now - fans spinning all the time and the machine getting very hot. It would be great to see a fix for this.
Same for me : I've just updated to 2.6.1 and CPU is jumping all the time to 20-40%. With more keychain access !
Same. Cpu load is always around 10%...
I'm still getting very high cpu usage on 2.6.4stable (build 20200303). It's much more intermittent now, but every 30 seconds or so it spins up to 100% CPU usage and locks the gui entirely. This is making the gui very difficult to use. It's not very inspiring that this issue has persisted over multiple major releases of the client.
I'm on macOS Mojave 10.14.5
Most helpful comment
Thanks @solick - I switched back to 2.5.0, but it's true that it's too heavy, I'll give 2.3.3 a try. I'd expect more people complaining about this.