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

Client delays folder renaming in explorer #841

Closed
liayn opened this issue Nov 10, 2016 · 4 comments
Closed

Client delays folder renaming in explorer #841

liayn opened this issue Nov 10, 2016 · 4 comments

Comments

@liayn
Copy link

liayn commented Nov 10, 2016

On windows version 6.0 causes some heavy delays to the system (explorer even freezes) when renaming folders. It does not matter whether the folder is inside the seafile storage. Any folder renaming on any path in the system is delayed. Sometimes 15 seconds and longer.
Closing the client lets the problem go away immediately.

@lins05
Copy link
Contributor

lins05 commented Nov 11, 2016

When it happens, can you check what's in the logs files? especially:

  • C:/Users/yourname/ccnet/logs/applet.log
  • C:/Users/yourname/ccnet/logs/seafile.log
  • C:/Users/yourname/seaf_ext.log

@liayn
Copy link
Author

liayn commented Nov 11, 2016

Neither of those log files shows anything in this regard unfortunately

@StoneGuo
Copy link

NOW I WANT TO DESIGN A ICON OVERLAY PLUGGIN.

2016-11-11 14:30 GMT+08:00 Shuai Lin notifications@github.com:

When it happens, can you check what's in the logs files? especially:

  • C:/Users/yourname/ccnet/logs/applet.log
  • C:/Users/yourname/ccnet/logs/seafile.log
  • C:/Users/yourname/seaf_ext.log


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#841 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUME2AAk7HjNITK1u-1SvoBmP01eeNWmks5q9AubgaJpZM4KudzC
.

@liayn
Copy link
Author

liayn commented Nov 12, 2016

Weird thing. Today, Seafile client is not running, I seem to have similar issues.
Seems that it could be a bad mix of of explorer extensions that somehow triggers that issue and none of the products is guilty at all. I'll close this issue for the time being.

@liayn liayn closed this as completed Nov 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants