Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Level 1

4 points

Dock uses 320% CPU after 10.7.2 update

After upgrading to 10.7.2, and after some time suddenly Dock takes all the CPU and gets unresponsible. killall Dock on terminal does not seem to really kill the task, so I have to reboot to get it solved. After some time the problem repeats.

Console events are quite concerning:

14/10/11 11:11:08,045 mds: (Error) FMW: WE ARE DROPPING FMW EVENTS!

14/10/11 11:11:08,046 mds: (Error) FMW: WE ARE DROPPING FMW EVENTS!

14/10/11 11:11:08,046 coreservicesd: FMOD WATCH EVENTS DROPPED!

14/10/11 11:11:08,048 mds: (Error) FMW: WE ARE DROPPING FMW EVENTS!

14/10/11 11:11:08,048 coreservicesd: FMOD WATCH EVENTS DROPPED!

14/10/11 11:11:08,067 com.apple.launchd.peruser.501: (com.apple.pbs) Throttling respawn: Will start in 1 seconds

14/10/11 11:11:08,071 mds: (Error) FMW: WE ARE DROPPING FMW EVENTS!

14/10/11 11:11:08,082 coreservicesd: FMOD WATCH EVENTS DROPPED!

14/10/11 11:11:08,104 com.apple.launchd.peruser.501: (com.apple.pbs) Throttling respawn: Will start in 1 seconds

14/10/11 11:11:08,128 mds: (Error) FMW: WE ARE DROPPING FMW EVENTS!

14/10/11 11:11:08,155 coreservicesd: FMOD WATCH EVENTS DROPPED!

14/10/11 11:11:08,155 mds: (Error) FMW: WE ARE DROPPING FMW EVENTS!

14/10/11 11:11:08,178 com.apple.launchd.peruser.501: (com.apple.pbs) Throttling respawn: Will start in 1 seconds

14/10/11 11:11:08,175 mds: (Error) FMW: WE ARE DROPPING FMW EVENTS!

14/10/11 11:11:08,178 mds: (Error) FMW: WE ARE DROPPING FMW EVENTS!

14/10/11 11:11:08,181 coreservicesd: FMOD WATCH EVENTS DROPPED!

Any idea on what can I do to solve it?

MacBook Pro, Mac OS X (10.7.2)

Posted on Oct 14, 2011 3:11 AM

48 replies

Nov 16, 2012 2:37 AM in response to watski

I tried deactiving Dropbox, Google Drive, Evernote, Bluetooth, it all didn't help. I don't have VMware or Parallels.

But deleting the db file ~/Library/Application Support/Dock/*.db seems to have worked for me too.

J.Kubi

Level 1

0 points

Sep 4, 2013 3:07 PM in response to Mark Thacker

Same basic solution here, but mine was just in an OU in AD which set a default desktop, which for some reason the Mac was refusing to access the share it was stored.

MzLortta

Level 1

27 points

Aug 25, 2014 12:25 PM in response to CoolDixon

Update. Using 10.7.2 …. I've done everything suggested in this and other posts about the dock using too much memory. Deleting the plist, etc. worked twice, but periodically the dock ***** memory like crazy and the fan goes crazy. Whats working since is then is to repair permissions and either logout or reboot. Has worked every time so far after a month or so.

Dock uses 320% CPU after 10.7.2 update