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

Application freezing after file download completes #8676

Closed
cyberduck opened this issue Mar 17, 2015 · 3 comments
Closed

Application freezing after file download completes #8676

cyberduck opened this issue Mar 17, 2015 · 3 comments

Comments

@cyberduck
Copy link
Collaborator

cyberduck commented Mar 17, 2015

5e4fc9a created the issue

Version 4.7 (17149), Mac OSX 10.10.2, connecting to a linux server (GoDaddy), PASSIVE mode, SFTP

For a period of time (about 1-2 min) after a file transfer the Cyberduck app "Browser" window items are unselectable. Then selecting "Bookmarks" and attempting to connect with a bookmarked server, the book mark is unselectable. After about 1-2min the items become responsive and seemingly in correct working order again.

I repeated this sequence twice in a row: Open a bookmarked server, highlight a file with mouse and drag it to a subfolder on my local desktop. The file is transferred, the logs show nominal activity. All of the files and folders in the Cyberduck browser window are un-selectable, bookmarks button is selected, none of the bookmarks are selectable. After a time period of 1-2min after the file transfer is finished (and when the bookmarks button was not selected), then the folders & files become selectable again - seemingly with no other input or change.

This problem has been happening on an off over the last few weeks with the last few versions of Cyberduck.

Note: my Mac is experiencing the documented Yosemite folder-unresponsive bug (i.e. when you create a new folder, drag items to it, then the folder shows no items, until you leave the directory and come back, then the items are show. Don't know if these are related somehow via system libs, but thought it might help in tracking down the problem.

Note 2: GoDaddy FTP server is a bit flaky and has periodic slow-downs 4KB/sec. Requires passive mode, and seems to like SFTP better than FTP. But it is mostly a flaky ftp service.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Mar 31, 2015

@dkocher commented

Can you find any related output in the system.log (/Applications/Utilities/Console.app)?

@cyberduck
Copy link
Collaborator Author

cyberduck commented Mar 31, 2015

@dkocher commented

Can you try if you can reproduce this issue when running on a guest account on your Mac.

@cyberduck
Copy link
Collaborator Author

cyberduck commented Apr 1, 2015

5e4fc9a commented

Can you find any related output in the system.log (/Applications/Utilities/Console.app)?
Can you try if you can reproduce this issue when running on a guest account on your Mac.

RE logs
Sorry I have no logs of the events. The Cyberduck log window shows no messages during the multiple freeze events.

RE guest account (aka OSX preferences testing)
Sorry, since the problem is intermittent, I don't have the ability to work from a guest account for an extended period.

RE: worksforme status
Probably not terribly applicable in the case of an intermittent failure. What I can tell you to look for though is a non-standard communication directive from a host like GoDaddy. They have been having severe problems with their FTP - it is documented and causing multiple prob reports for GoDaddy - this is obviously a problem with GoDaddy. However, when GoDaddy-FTP issues some sort of non-standard command, in general, an FTP client should not be expected to freeze for 90sec - there should be a "connection" warning or error, but freezing for 60-90 secs then unfreezing is non-intuitive behavior and suggests an error condition not being anticipated.

This is all I can offer. GoDaddy tech "support" is not being terribly supportive - they claim I should just stop using Cyberduck (which is my favorite FTP client BTW) - but they also claim they are working on their FTP issues.

Sorry, this is all I have for you.

@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

1 participant