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 responds slow and crashes often #9201

Closed
cyberduck opened this issue Jan 6, 2016 · 2 comments
Closed

Application responds slow and crashes often #9201

cyberduck opened this issue Jan 6, 2016 · 2 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jan 6, 2016

94e1286 created the issue

Hi,

I am having issues related to application response (e.g. switching from application X to cyberduck, choosing different files on the cyberduck window ...) as well as cyberduck getting non-responsive and crashing often (~10% of launches maybe). I found a quite old post that mentions long transfer lists being an issue (which I clear, whenever I get a warning now) but not much else. Is anyone else experiencing this or have some suggestions?

Thanks!

ps. I've been having this issue for a couple of months now and the latest update to 4.7.3 didn't help.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 18, 2016

@dkocher commented

Please attach the crash report and any related output in the system.log (/Applications/Utilities/Console.app).

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 21, 2016

@dkocher commented

Please update to the latest snapshot build available. If the issue persists, please attach any related output in the system.log (/Applications/Utilities/Console.app).

Loading

@cyberduck cyberduck closed this Jan 21, 2016
@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
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant