Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I'm writing my doctoral thesis on a Macbook pro using MS Word 2011 and Endnote X6 (Mac Word and Endnote on the newest version). Word responses really slowly to any input like typing or scrolling, with a delay of sometimes more than 4 seconds. Super annoying. My google-research on the problem led to the conclusion that there is no resolution yet. BUT: a workaround is to kill the process "appleeventsd" in Activity Monitor.

And that works super well, killing it lets word respond immediately again, without any delay.

Now my problem: appleeventsd starts again after a couple of minutes, sometimes just 2. This is really annoying because I can't really concentrate on working for a longer period of time as I always get interrupted by having to kill appleeventsd.

Does anybody have an idea how to fix this? What is appleeventsd doing for me? Do I even need it? Could I completely delete it from my system in order to prevent it from starting again? Or can I at least prevent it from restarting after I killed it so I can focus on working without interruptions?

Thank you so much for your help!!

Alek

share|improve this question
    
It's a known bug with the Apple Events Daemon in 10.8.2 which affects lots of apps, and I doubt you can do anything to fix it besides running sudo killall -KILL appleeventsd repeatedly and waiting for Apple to release an update. –  Karan Mar 2 '13 at 23:50
    
do you know a way to kill it automatically? What is actually annoying is having to do it by myself all the time. –  Al Ek Mar 3 '13 at 0:10
    
like a script or so? –  Al Ek Mar 3 '13 at 0:19
    
I guess you can use something like cron (here's a free frontend) or launchd or perhaps even Automator to repeatedly run the killall command. Apple.SE would be a good place to ask. –  Karan Mar 3 '13 at 0:53
    
Hey, I was trying cronix but it always crashed unexpectedly. –  Al Ek Mar 3 '13 at 13:36

1 Answer 1

The origin: a bug in OSX 10.8.2
This problem is caused by a bug in Mac OSX 10.8.2 (also more info here). It should be solved in 10.8.3, although the 10.8.3 release info from Apple makes no mention about resolving this bug. Some users reported it to be back in 10.9.0.

Current situation
As the current release (at the time of this post) is 10.9.5 (released 17 September 2014) is already some subversions past 10.9.0 and I can't find any recent new information about this bug, I think it's safe to assume that the bug currently isn't present anymore.

The solution
The best solution would be to update your Mac to the most recent update of OSX.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.