The same happens to me on Windows 10. The behaviour is reproducible on different Windows PCs connected to the same account with the same version of the client. The endless syncing keeps ca. 50% of my CPU power busy all the time (causes large energy consumption, heat production, noisiness etc.). A fix would be greatly appreciated.
Synchronization should be started only when:
the client is launched
changes are made either on the server or locally
synchronization is unpaused
synchronization is forced manually.
When errors occur during the last sync, the client might re-try the synchronization once again. But when exactly the same errors occur, the client should give up and wait for any local or remote changes. There is no use in re-trying the (failed) synchronization over and over again.
Immediately after a finished synchronization (with errors) a new synchronization is started although there are no local nor remote changes. On the client screen with my account and synchronized folders it reads chronologically (translated from Czech):
Looking for changes in /loops/through/folders/where/errors/occured
The same problem occurs with the client version 2.9.1 (build 5500). As I mentioned earlier, I am experiencing an unbearable computational load (on the client side) whenever the OwnCloud client is running with unpaused synchronization.
For now I keep the synchronization paused, and only unpause it for a single sync run when I want to upload local changes or download remote changes. Another options would be to simply downgrade to an older version of the client, perhaps 2.8.2, or just launch the Command Line Client at regular time intervals (e.g. every 10 minutes). The latter could be achieved with few lines a simple script.
Any other ideas? Is there any way to make the desktop client sync ONLY when there are new local or remote changes? I thought this was the primary purpose of the desktop app. Should this issue not be more important than any fancy features like virtual files or colourful file icons (#9026)? A quick & dirty fix would be to provide an option to limit the maximum frequency of synchronizations.
Apologies to anyone who might find this post balancing on the edge of politeness. It might indeed reflect some frustration, but no offence is intended. I appreciate the kind and patient work of the OwnCloud community.