Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Permanent Sync & high CPU load on MacOS #1274

Closed
solick opened this issue May 27, 2019 · 18 comments
Closed

Permanent Sync & high CPU load on MacOS #1274

solick opened this issue May 27, 2019 · 18 comments

Comments

@solick
Copy link

solick commented May 27, 2019

Nextcloud 2.5.2 client for MacOS uses permanent high cpu load (> 95%) and never stops syncing.

Expected behaviour

Should not use much CPU capacity. have periods where client does not need to sync

Actual behaviour

Is permanently syncing & consumes more than 95% cpu load

Steps to reproduce

  1. Have 2 NC server under management
  2. just sync

Client configuration

Client version: 2.5.2

Operating system: MacOS 10.14.5

OS language: German

Installation path of client:

Server configuration

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):

@ja573
Copy link

ja573 commented May 30, 2019

Does it actually sync? Some people (including me) are experiencing #1133 in linux

@solick
Copy link
Author

solick commented Jun 5, 2019

@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

@ja573
Copy link

ja573 commented Jun 6, 2019

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.

@bruman
Copy link

bruman commented Jul 2, 2019

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.

@solick
Copy link
Author

solick commented Jul 17, 2019

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?

@ja573
Copy link

ja573 commented Jul 17, 2019

Well I guess that's needed for consistency - the question is why is it faster in previous versions 🤔

@solick
Copy link
Author

solick commented Jul 29, 2019

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!

@samuel-emrys
Copy link

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?

@misch7
Copy link
Member

misch7 commented Oct 21, 2019

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?

@vpiskunov
Copy link

vpiskunov commented Dec 19, 2019

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

@Upperholme
Copy link

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.

@ad5030
Copy link

ad5030 commented Dec 22, 2019

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 !

@mibocs
Copy link

mibocs commented Jan 8, 2020

Same. Cpu load is always around 10%...

@samuel-emrys
Copy link

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

@mgallien
Copy link
Collaborator

mgallien commented Jan 5, 2022

@solick could you please test again with our latest release (3.4.1 at the moment) ?

@github-actions
Copy link

github-actions bot commented Feb 2, 2022

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

@github-actions
Copy link

This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you!

@mibocs
Copy link

mibocs commented Apr 4, 2022

@mgallien

could you please test again with our latest release (3.4.1 at the moment) ?

I have tested it with version 3.4.4 and CPU usage is now 0 i.e zero, so it seems to be working well. Good job, Big THANKS!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests