6252676 commented

More investigation....seems to turn itself off when the first file uploading is finished, even if there are other files still in process.

6252676 commented

Additionally, the transfer screen shows "Transfer incomplete 0 of 0KB" but the first file is clearly uploaded.

@dkocher commented

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

6252676 commented

No...no output in the system log for 4 months, about anything! Thanks for sending me there to look.

It seems to be a very consistent behavior...worked with it more yesterday. One file will upload well, and program will turn off. Two files will appear to be uploading well, but when the first is done, the other will abort as the program turns off. I have tried different type and sizes of files. I have checked and unchecked the "close when transfer completes" preference. Doesn't seem to behave differently either way.

647db35 commented

...This is the same problem I reported in ticker #6309.

Yesterday I successfull uploaded a 125MB big file, but after tranfer the application quitted with no messages.
Sometimes it crashes when, with a FTP connection open, i'm not uploading or downloading (I use to edit breaf code by Smultron via Cyberduck: it quits during editing).

647db35 commented

Replying to [comment:3 dkocher]:

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

Console outputs to me strings like that:

29/10/11 19:59:05 com.apple.launchd[77] ([0x0-0x23023].ch.sudo.cyberduck[938]) Exited abnormally: Broken pipe 
29/10/11 20:19:02 com.apple.launchd[77] ([0x0-0x25025].ch.sudo.cyberduck[970]) Exited abnormally: Broken pipe 

Other output reports on ticker #6309

@dkocher commented

#6331 closed as duplicate.

@dkocher commented

#6309 closed as duplicate.

@dkocher commented

Please attach the crash report.

647db35 commented

Replying to [comment:9 dkocher]:

Please attach the crash report.

Sorry... NO CRASH REPORT appear to me: Cyberduck crasches about 10 times/day, it simply self-quit with no warnings.

6252676 commented

I, as well, don't get or don't know where to get a crash report. I'm finding that it only works if I upload one file at a time, and restart it after each upload. This is a very different tool than the one I used to have. Can I reinstall the earlier version that worked really well?

Gautehk commented

Old releases can be downloaded from http://cyberduck.ch/changelog/

I installed 4.1 this morning. No crashes so far.

647db35 commented

Replying to [comment:12 Gautehk]:

Old releases can be downloaded from http://cyberduck.ch/changelog/

I installed 4.1 this morning. No crashes so far.

Thanks Gautehk for the link. Just downgraded. Hope developers to find the bug, meanwhile this is a good solution.

6252676 commented

Just installed 4.1. Sent four files at once, and all were successful with no crash. Seems to be working the way it used to. So happy to have it back! Thank you.

@dkocher commented

Is everyone here having this issue on OS X 10.5?

@dkocher commented

Please update to the latest snapshot build available and let me know if the issue persists.

Gautehk commented

I upgraded to the snapshot, and Cyberduck started crashing again. I have work to do, so I downgraded again. If you can advise me how to get a crash report other than the one line in system.log, I will test again.

The crashes were triggered by dragging a file to Cyberduck, and by clicking the "up" button to navigate to the parent folder. These events are just like the crashes I experienced earlier. Cyberduck do not crash every time I do this, but frequently.

Yes, this computer runs OS X 10.5.

Gautehk commented

Tried 4.2.1. Crashes still occur.

@dkocher commented

#6432 closed as duplicate.

@dkocher commented

Duplicate for #6863.