The basic outline of the problem is that sometimes a particular application will get into a state where any events sent to it using
AESend, for that matter) would not be delivered to the target application, and
AESendMessagewould simply block until the timeout value was reached, then return an
This affected his iPhoto Library Manager as well as e-mail clients such as MailMate, Postbox, and GyazMail communicating with SpamSieve. The bug can also affect TotalFinder and applications that use the ODBEditor events.
As a short-term fix, you can log out of your Mac or kill the appleeventsd process. Medium-term, the applications sending the events can be rewritten to use
typeKernelProcessID rather than
typeApplicationBundleID to specify the target application. Of course, we hope that Apple will eventually fix the bug.
Update (2012-10-05): This bug also seems to cause hangs at launch for applications using the Growl 1.3 SDK.
Update (2013-03-16): The bug appears to be fixed in Mac OS X 10.8.3.
Update (2013-10-29): It looks like this bug may be back in Mac OS X 10.9 Mavericks.
Stay up-to-date by subscribing to the Comments RSS Feed for this post.