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

OSX: Stops synching often, no message (might be 'sleep' related) #1693

Open
boekabart opened this issue Jun 9, 2016 · 7 comments
Open

OSX: Stops synching often, no message (might be 'sleep' related) #1693

boekabart opened this issue Jun 9, 2016 · 7 comments
Labels
bug up-for-grabs A good issue for new contributors

Comments

@boekabart
Copy link

I often notice that Sparkleshare hasn't update any of my (2) repositories for a day or more. Says 'synced Tuesday' for example. No way to trigger it to update, and when I try to close Sparkleshare, it hangs at 99.9% CPU and I have to use Activity Monitor to kill it.
I do let my laptop sleep often, so it might be related to that.

@markusstoll
Copy link
Contributor

Hi,

I am glad, that I am not the only one, so I can confirm this. I use SparkleShare with 2 desktop Macs and one Macbook. This problem only occurs on the mobile system and I too suspect a correlation with sleep/awake or with situations with missing network connections.
Most often I halt to kill and restart SparkleShare

Markus

Am 09.06.2016 um 10:35 schrieb Bart de Boer notifications@github.com:

I often notice that Sparkleshare hasn't update any of my (2) repositories for a day or more. Says 'synced Tuesday' for example. No way to trigger it to update, and when I try to close Sparkleshare, it hangs at 99.9% CPU and I have to use Activity Monitor to kill it.
I do let my laptop sleep often, so it might be related to that.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@hbons
Copy link
Owner

hbons commented Jun 9, 2016

Were there actually new changes on the remote or is it that the status message is confusing (it tells you when it was last synced)?

@markusstoll
Copy link
Contributor

for me this happens most often when local changes are being sent

Markus

Am 09.06.2016 um 13:37 schrieb Hylke Bons notifications@github.com:

Were there actually new changes on the remote or is it that the status message is confusing (it tells you when it was last synced)?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@boekabart
Copy link
Author

I my case I always notice the issue because I miss remote changes that my colleagues tell me I should be able to find. So yes, there are new changes.
(now that you ask, the 'status' in each of the menus for the remotes is confusing: 'synched tuesday' for me as user sounds like 'last check' took place at that time. )
So I guess the status message itself has nothing to do with the bug per se, as there seems to be no way to check when SS actually last checked the remote.
But fact is, is that it stops receiveing remote updates and when that happens, hangs at 100%cpu when trying to shut down.

@palomnik
Copy link

palomnik commented Jul 25, 2016

I have had this problem, but I have one repository that is in download mode for hours with nothing happening. I tried deleting and re-adding the repository on the client, and it downloads about half of it and then freezes. I am stuck and unable to get the repository back on the mac.

I don't know if there is a big file causing the problem or what. Is there a way to manually get around this problem?

Note: this is on a Macbook Air.

@fmartingr
Copy link

This just happened to me after wakeup on macOS 10.12 & Sparkleshare 1.5.0 exactly as described by @boekabart.

@hbons hbons added bug up-for-grabs A good issue for new contributors labels Sep 20, 2016
@boekabart
Copy link
Author

Since upgrade to macOS sierra, it always hangs after a local change. Need to restart sparkleshare will sync once, but never auto-syncs anymore

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug up-for-grabs A good issue for new contributors
Projects
None yet
Development

No branches or pull requests

5 participants