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

Nextcloud Desktop client on macOS sync slow, freezes and resumes #4181

Closed
jcastro opened this issue Jan 17, 2022 · 13 comments
Closed

Nextcloud Desktop client on macOS sync slow, freezes and resumes #4181

jcastro opened this issue Jan 17, 2022 · 13 comments

Comments

@jcastro
Copy link

jcastro commented Jan 17, 2022

How to use GitHub

  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Expected behaviour

Files should be synced continuously

Actual behaviour

Files are being synced, then all activity is stoped for a few minutes and then it restarts again for a bit, the cycle repeats

Steps to reproduce

  1. Select a bunch of folders with many files to sync
  2. Wait for the sync process to start

Client configuration

Client version:

Operating system: macOS Monterrey 12.1 Macbook Pro 14 M1 Pro

OS language: English

Desktop client macOS osx-21.2.0 version 3.4.1

Server configuration

Nextcloud version: Nextcloud Hub II (23.0.0) - TrueNAS plugin

Storage backend (external storage): TrueNAS

Logs

  1. Client logfile:
    Download logs: https://d.pr/f/QmTDy2

  2. Web server error log:
    Download logs: https://d.pr/f/VPhN5T

  3. Server logfile: nextcloud log (data/nextcloud.log):
    Download logs: https://d.pr/f/N0fiPu

There's also a video that shows the behaviour, you can fast forward it to see what's happening. The terminal window shows the resources and process used in the nextcloud server. There's also no IO wait, the server is barely used when the video was recorded and it's running on a NVME drive for the database. The network widget shows the activity in the macOS client, which as you can see aside from nextcloud barely has any activity

Screen.Capture.on.2022-01-17.at.13-08-24.mp4
@jcastro
Copy link
Author

jcastro commented Jan 18, 2022

Rolling back to Desktop client version 3.3.6 seems to solve the problem

@allexzander
Copy link
Contributor

Probably related to #4106

@snowflakeas
Copy link

same problem new NC23.0 install
client 3.3.6 seems to solve this (slow, but at least moves forward)

@jcastro
Copy link
Author

jcastro commented Feb 9, 2022

@allexzander should this be fixed on 3.4.2? thanks!

@jcastro
Copy link
Author

jcastro commented Feb 27, 2022

Just a heads up that release 3.4.3 didn't fix this issue

@jcastro
Copy link
Author

jcastro commented Mar 7, 2022

3.4.3 working very bad, had to go back to 3.3.6

@jcastro
Copy link
Author

jcastro commented Mar 21, 2022

3.4.4 still has the issue

@nioakeim
Copy link

nioakeim commented Apr 2, 2022

I noticed the same issue on a large sync operation. for 44Gb sync with the 3.4.4 I was waiting for hours, but with 3.3.6 it just finished under 20 minutes. To bad that 3.4.4 is the intel version

@jcastro
Copy link
Author

jcastro commented Apr 4, 2022

3.5 rc1 still with the issue, had to go back to 3.3.6

@jcastro
Copy link
Author

jcastro commented Apr 11, 2022

3.5 rc3 still with the issue, had to go back to 3.3.6

@github-actions
Copy link

github-actions bot commented May 9, 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 github-actions bot added the stale label May 9, 2022
@jcastro
Copy link
Author

jcastro commented May 9, 2022

3.5 still wit hthe issue sadly

@github-actions github-actions bot removed the stale label May 10, 2022
@jcastro
Copy link
Author

jcastro commented May 19, 2022

3.5.1 seems to fix the issue, can't reproduce anymore. Thanks!

@jcastro jcastro closed this as completed May 19, 2022
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

5 participants