You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ever since I have upgraded to 5.2.1, Cyberduck crashes whenever I try to upload or download files to any FTP servers in my bookmarks. This problem happens whether I use the transfer icons or by drag and dropping files. The application window freezes, my CPU overload bars go up, and a few seconds later Cyberduck crashes.
I'm running Mac OS X 10.5.8 on a Mac Intel. Restarting the Mac and repairing the authorizations didn't help.
Any suggestions?
The text was updated successfully, but these errors were encountered:
Thank you for your quick reply. I've downloaded the latest nightly build -- 3.3b1 (5202). I run it from the Desktop and didn't put it on top of the other version.
The crashes seem to have disappeared. I've been able to download and upload a few files from different FTP serveurs. The build is extremely slow -- when you click on a transfer button, it takes a minute or two before the transfer actually starts -- but I suppose that nightly builds aren't optimized for speed.
There are still some performance issues in the 3.3 branch. A minute or two seems to very long though. Do you have a huge list of old transfers in your Transfers window which could cause that?
You're absolutely correct -- I had a pretty huge list of old transfers, it actually took my Mac Pro almost a minute to execute the select all command. I wiped out the history, and now Cyberduck is extremely more responsive.
hello,
Ever since I have upgraded to 5.2.1, Cyberduck crashes whenever I try to upload or download files to any FTP servers in my bookmarks. This problem happens whether I use the transfer icons or by drag and dropping files. The application window freezes, my CPU overload bars go up, and a few seconds later Cyberduck crashes.
I'm running Mac OS X 10.5.8 on a Mac Intel. Restarting the Mac and repairing the authorizations didn't help.
Any suggestions?
The text was updated successfully, but these errors were encountered: