Application hangs editing file in external editor

[cyberduck]

Lkmnyc created the issue

I have tried everything I know but can't figure out if there are preferences on Mac OSX to delete - I haven't found them. I am no longer able to work on the server, i.e., open a file using an external editor (Textwrangler). I get the spinning beach ball and have to force quit.

This is a blocker, thus highest priority for me, because I need to find another FTP app until I can use this again, and Cyberduck is my preferred application.

Any help will be appreciated.

[cyberduck]

Kkwan4 commented

I have the same issue as well

my environment is : OS X 10.8.2

cyberduck version : 4.2.1

text wrangler version : 4.0.1

smultron version : 3.5



I've noticed the following issue and it's related to Cyberduck opening in text wrangler

• reboot Mac

• start Cyberduck (configured for text wrangler)

• select file to edit

• Cyberduck launches text wrangler and opens up file



Here's where it gets interesting

• close text wrangler

• select file to edit from Cyberduck

• spinning beach ball shows up



• kill Cyberduck

• relaunch Cyberduck and configure external text editor as Smultron

• select file to edit from Cyberduck

• works



This appears to be something specific with Text Wrangler and Cyberduck... as Smultron worked.



After playing with this for a while, Smultron has failed to work as well as Text Wrangler. A reboot allows these to work again, but only shortly

[cyberduck]

04e45c0 commented

Mac OS 10.8.2, Cyberduck 4.2.1 (tested with release 9350 and 9684), Textwrangler 4.0.1 (release 3152)

Same here.

Found that ticket (http://trac.cyberduck.ch/ticket/6093) where it was recommended as a workaround „to disable the ODB editor support and instead work with the file notifications editor support“. Open Terminal:

defaults write ch.sudo.cyberduck editor.odb.enable false

That worked for me. But as I’m just a user, I don’t know what this change finally effects.

PS: Seems to me this problem came up with updating to Mac OS 10.8.2 ...

[cyberduck]

Kkwan4 commented

the work around works

I can confirm that this is an issue with 10.8.2

I have another machine still on 10.8.1 not having this issue.

[cyberduck]

@dkocher commented

#6885 closed as duplicate.

[cyberduck]

@dkocher commented

I cannot replicate this issue. Can you also test with the latest snapshot build available. Can you find any related output in the system.log (/Applications/Utilities/Console.app)?

[cyberduck]

Kkwan4 commented

I tested with the latest 4.2.2 (9757) snapshot build and it provided the same effect, strangely no logs under console.app.

This was how I tested

• I re-enabled odb via

defaults write ch.sudo.cyberduck editor.odb.enable true

• configured Cyberduck with the lastest snapshot build

• updated to the latest snapshot build

• installed and restarted

• opened up sftp connection and highlight a file to edit

• click the text wrangler edit icon

• cyberduck causes text wrangler to startup and launch

• cyberduck will display spinning beach ball for about 5-10minutes, then return to normal idle state



no logs found under console.app other than these update requests

12/9/26 10:10:22.498 AM Cyberduck[8947]: Sparkle Error: An error occurred in retrieving update information. Please try again later.
12/9/26 10:10:22.498 AM Cyberduck[8947]: Sparkle Error (continued): The operation couldn’t be completed. (NSURLErrorDomain error -1100.)

These logs were generated before I changed the setting to update with latest snapshot build



When I disable odb via

defaults write ch.sudo.cyberduck editor.odb.enable false

I'm able to click the text wrangler edit icon and it appears to be working again where I can edit/save and it will update the remote file


I hope this helps.

[cyberduck]

Brett Francis commented

I have effectively the same issue but when using CyberDuck 4.2.1, BBEdit 10.1.2 and Mac OS X 10.8.2

The moment I try to "Edit With..." BBEdit I get a spinning beach-ball of death and according to the Force Quit menu CyberDuck immediately becomes an "Application Not Responding".

Replying to [comment:1 Kkwan4]:

my environment is : OS X 10.8.2

cyberduck version : 4.2.1

text wrangler version : 4.0.1

smultron version : 3.5

[cyberduck]

66ef503 commented

It looks like this is being worked on, but I'll also add that this happens with Fraise.

OS X 10.8.2
Cyberduck 4.2.2 (9796)

[cyberduck]

@dkocher commented

#6877 closed as duplicate.

[cyberduck]

@dkocher commented

#6897 closed as duplicate with hang report attached.

  Thread 0xa162f    priority 46        
15 Java_ch_cyberduck_ui_cocoa_odb_ODBEditor_edit + 223 (libODBEdit.dylib) [0x32f786af]
  15 -[ODBEditor editFile:options:forClient:context:] + 70 (libODBEdit.dylib) [0x32f78ade]
    15 -[ODBEditor(Private) _editFile:isEditingString:options:forClient:context:] + 496 (libODBEdit.dylib) [0x32f78fc4]
      15 AESend + 87 (HIToolbox) [0x96fa0949]
        15 aeSend + 218 (AE) [0x97fff577]
          15 AESendMessage + 5872 (AE) [0x97fd9dc3]
            15 CFRunLoopRunInMode + 123 (CoreFoundation) [0x97b824ab]
              15 CFRunLoopRunSpecific + 378 (CoreFoundation) [0x97b8263a]
                15 __CFRunLoopRun + 1247 (CoreFoundation) [0x97b82f7f]
                  15 __CFRunLoopServiceMachPort + 185 (CoreFoundation) [0x97b7d599]
                    15 mach_msg_trap + 10 (libsystem_kernel.dylib) [0x90ced7d2]
                     -15 ipc_mqueue_receive_continue + 0 (mach_kernel) [0xffffff8000213030]


Process:         appleeventsd [63]
Path:            /System/Library/CoreServices/appleeventsd
Architecture:    x86_64
Parent:          launchd [1]
UID:             71
Sudden Term:     Dirty (allows idle exit)
Task size:       904 pages

  Thread 0x310      DispatchQueue 2          priority 33        
  15 _dispatch_mgr_thread + 54 (libdispatch.dylib) [0x7fff955be9ee]
    15 kevent + 10 (libsystem_kernel.dylib) [0x7fff8ef49d16]
     -15 ??? (mach_kernel + 3471600) [0xffffff800054f8f0]

  Thread 0x311      DispatchQueue 7          priority 31        
  15 _dispatch_sig_thread + 45 (libdispatch.dylib) [0x7fff955bbd85]
    15 __sigsuspend_nocancel + 10 (libsystem_kernel.dylib) [0x7fff8ef49566]
     -15 ??? (mach_kernel + 3581216) [0xffffff800056a520]

  Binary Images:
         0x1072da000 -        0x1072dafff  appleeventsd <4617FC4D-4C6C-3B62-9E64-08F9C99ABEEF> /System/Library/CoreServices/appleeventsd
      0x7fff8ef37000 -     0x7fff8ef52ff7  libsystem_kernel.dylib <C0535565-35D1-31A7-A744-63D9F10F12A4> /usr/lib/system/libsystem_kernel.dylib
      0x7fff955ba000 -     0x7fff955cfff7  libdispatch.dylib <D26996BF-FC57-39EB-8829-F63585561E09> /usr/lib/system/libdispatch.dylib
 -0xffffff8000200000 - 0xffffff800074033c  mach_kernel <69A5853F-375A-3EF4-9247-478FD0247333> /mach_kernel

[cyberduck]

@dkocher commented

It is either appleeventsd that or the editor receiving the event that is blocking.

[cyberduck]

@dkocher commented

Replying to [comment:14 dkocher]:

It is either appleeventsd that or the editor receiving the event that is blocking.

We are using the default timeout in AESend which is defined as

  kAEDefaultTimeout             = -1,   /* timeout value determined by AEM */

We should change that to a sensible default.

[cyberduck]

@dkocher commented

A third party filed rdar://12424662 describing the exact same issue. Looks like this bug was introduced in 10.8.2.

[cyberduck]

@dkocher commented

Timeout set in b179031.

[cyberduck]

Blomberg Samuel commented

Can confirm that editing a file with Espresso is also causing Cyberduck to hang.

defaults write ch.sudo.cyberduck editor.odb.enable true

This workaround alleviates the hang, but I would also like to know what the downsides are (if any) of using said workaround until an official fix is implemented.

• OS: Mac OSX 10.8.2

• Cyberduck: 4.2.1