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

Cyberduck crashes with synchronize #1000

Closed
cyberduck opened this issue Jan 17, 2007 · 3 comments
Closed

Cyberduck crashes with synchronize #1000

cyberduck opened this issue Jan 17, 2007 · 3 comments
Assignees
Milestone

Comments

@cyberduck
Copy link
Collaborator

lsievert created the issue

HI, I'm trying to use the synchronize function and it keeps causing Cyberduck to crash. I am able to pick the two directories, one remote and one local, to sync, but almost as soon as it starts working, CyberDuck quits without any errors and without generating any of those "log an Apple report" dialog boxes.

Remote server is running linux. Mac is a PB G4 running latest Apple OS 10.

@cyberduck
Copy link
Collaborator Author

ce6063f commented

I'm having the same issue with the latest version of CyberDuck

It's not consistent - sometimes CyberDuck works ok, if it is going to crash, it does so (no crash log) immediately after the Sync confirmation window pops up.
It has also started to hang - after confirmation, it goes back to the transfer window with a "0B of Unknown size" message.
The stop button has no effect

@cyberduck
Copy link
Collaborator Author

6d5fa0e commented

I am also experiencing the same issue. I am running CyberDuck v2.7.2 and OS X 10.4.8 on a MacBook Pro with 2GB of memory. This is all happening on SFTP connections. It is effectively rendering the Synchronize feature useless. I am not sure why this is not a higher priority bug than just Normal.

I vote to raise the priority.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Please refer to #1011. Reopen #1011 if you can see this crash in the latest nightly build from http://update.cyberduck.ch/nightly/

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants