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
Frequent crashes in sftp sessions #2107
Comments
I've got the same error on Mac OS X 10.4.11 on a PowerBook G4 (PPC) using Cyberduck 3.0.1 (3999).
I've found that after beginning an action, perhaps after Cyberduck has been idle a time (or not, I can't remember), Cyberduck silently crashes, and disappears. There's virtually no extended hard drive activity. It simply disappears, and if I don't notice and attempt to go back to it, I can't find it (until I notice it's no longer active in the Dock). |
Please try the latest nightly build from (http://update.cyberduck.ch/nightly). |
Still occuring in ce3908e (the current nightly). Mac OS X 10.5.4 - MacBook Pro |
This is still occurring in the latest nightly build (4180).
I can reproduce it under SFTP by opening a file in my external editor (in my case TextWrangler), then as soon as the file opens, alt-tab back to CyberDuck and try to open another file. This causes the crash without fail on my system (OSX 10.5.4, Intel). If I wait a little while (as is usually the case when editing files), I can open another file as per usual. This is not the only circumstance under which it crashes, but usually the other times it happens is when I'm editing files and CyberDuck disappears in the background (and I'm left wondering why my website isn't updating). The issue is much harder to reproduce this way, but doesn't happen anywhere near as often. |
Please try the latest nightly build from (http://update.cyberduck.ch/nightly). Should be fixed with the resolution of #2142. |
Hi,
Version 3.0.1 has so far been very unstable on my iMac and my MacBook pro (both with intel cpus).
3.0 was not unstable at all in the same way.
I mostly run sftp sessions and Cyberduck quits at least one every 30-45 minutes.
The console has this to offer (no crashreporter log created), maybe it can be of some help:
The text was updated successfully, but these errors were encountered: