Cyberduck Mountain Duck CLI

#6309 closed defect (duplicate)

Cyberduck crashes without any error code

Reported by: paolobeccari Owned by:
Priority: high Milestone: 4.2
Component: core Version: 4.1.3
Severity: critical Keywords: crash
Cc: Architecture: Intel
Platform: Mac OS X 10.5

Description

Since I upgraded Cyberduck to Version 4.1.3 (9045) my beloved Cyberduck crashes suddenly and with any error message. It works for a while but it self-closes while i'm editing some file (via Smultron) or just while open a remote folder. It happened at least 15 times in 24 hours on two different machines (platform, architecture, and job is the same). I tried to fix the problem by deleting and reinstalling the application, but nothing changes.

these are some console reports:

15/10/11 13:55:46 com.apple.launchd[104] ([0x0-0x3c03c].ch.sudo.cyberduck[1517]) Exited abnormally: Broken pipe 
15/10/11 14:10:10 com.apple.launchd[104] ([0x0-0x42042].ch.sudo.cyberduck[1584]) Exited abnormally: Broken pipe 
15/10/11 15:17:00 [0x0-0x64064].ch.sudo.cyberduck[2207] 2011-10-15 15:17:00,779 [background-4] ERROR ch.cyberduck.core.ftp.FTPSession - Connection attempt canceled 
15/10/11 15:41:17 com.apple.launchd[104] ([0x0-0x64064].ch.sudo.cyberduck[2207]) Exited abnormally: Broken pipe 
15/10/11 16:00:44 com.apple.launchd[104] ([0x0-0x6f06f].ch.sudo.cyberduck[2437]) Exited abnormally: Broken pipe 
15/10/11 16:40:09 com.apple.launchd[104] ([0x0-0x7a07a].ch.sudo.cyberduck[2575]) Exited abnormally: Broken pipe 
15/10/11 16:53:19 Cyberduck[2974] handleClosedFileEvent: Got ODB editor event for unknown file. 
15/10/11 16:53:19 Cyberduck[2974] handleClosedFileEvent: Got ODB editor event for unknown file. 
15/10/11 16:53:19 Cyberduck[2974] handleClosedFileEvent: Got ODB editor event for unknown file. 
15/10/11 16:53:19 Cyberduck[2974] handleClosedFileEvent: Got ODB editor event for unknown file. 
15/10/11 17:00:32 com.apple.launchd[104] ([0x0-0x8e08e].ch.sudo.cyberduck[2974]) Exited abnormally: Broken pipe 

Change History (3)

comment:1 Changed on Oct 17, 2011 at 7:52:54 PM by paolobeccari

In the title I wanted to say that when Cyberduck crashes DOESN'T WRITE ANY ERROR CODE to warn about crash.

Meanwhile the problem still goes on.

Last edited on Oct 17, 2011 at 7:53:54 PM by paolobeccari (previous) (diff)

comment:2 Changed on Oct 28, 2011 at 4:42:59 PM by paolobeccari

  • Summary changed from Cyberduck crashes with any error code to Cyberduck crashes without any error code

comment:3 Changed on Oct 31, 2011 at 11:58:03 AM by dkocher

  • Milestone set to 4.1.4
  • Resolution set to duplicate
  • Status changed from new to closed

Closing as duplicate for #6328.

Note: See TracTickets for help on using tickets.
swiss made software