lsregister and dock - extremely high CPU activity

Question

Level 1

0 points

lsregister and dock - extremely high CPU activity

Since downloading Yosemite my MB Pro has been ticking overtime with extremely high CPU usage from 'dock' and 'lsregister', and sometimes 'mds'. Currently dock is running at 76% and lsregister running two instances of root and user at 40% each. The laptop is consistently getting hot, the fan is working overtime, and the battery lasts an hour if I'm lucky. Finder takes about a minute to show the files in any given folder...basically the system has slowed to a snails pace in favour of these new CPU hogs. I have tried to rebuild Launch Services through terminal and has visited many forums in search of a solution. Most of the advice was to rebuild the aforementioned and others to delete Launch Services pref. files from the Library. I have verified and fixed permissions and verified disk. I have a partitioned drive and have stopped spotlight indexing both partitions in an attempt to win back some speed to my system, but sadly I am not winning. Anyone with any advice would be greatly appreciated.

MacBook Pro (17-inch Mid 2009), OS X Yosemite (10.10)

Posted on Oct 26, 2014 2:00 AM

Reply

Answer 1

Seasailor Author

Level 1

0 points

Oct 26, 2014 2:21 AM in response to Seasailor

So just an update to this. I have double clicked the 2 instances of lsregister through Activity Monitor and 'quit' both processes. I do not yet know what problems this action may cause, but so far the system is running normally, however 'dock' is now showing a CPU usage of 99%, is this normal? Finder is still sluggish, but not as bad.

Reply

Answer 2

CharlieP

Level 1

4 points

Oct 27, 2014 7:45 AM in response to Seasailor

Had the same issue on Dock. Force Quit > Relaunch Finder does the trick.

Reply

Answer 3

Seasailor Author

Level 1

0 points

Oct 28, 2014 7:51 AM in response to CharlieP

Hi CharlieP, thanks for your message. Yes, tried that as well, and other similar actions. I attempted to fix it with Disk Warrior (new version) and the problem wouldn't budge. Every time I rebooted the lsregister and mds problem would come back. After spending a few more hours of research on it I felt there must have been a corrupt pref list somewhere since my update to Yosemite. I gave up on it and I carbon copied my drive and did a clean install and the problem has been fixed. Didn't want to go that route, but at least it's fixed now.

Reply

Answer 4

CharlieP

Level 1

4 points

Oct 28, 2014 7:53 AM in response to Seasailor

Ugh, I might have to do a clean install myself. Bummer. Thanks for the update that it worked, though. That's encouraging.

Reply

Answer 5

TomK2020

Level 1

10 points

Oct 29, 2014 8:09 PM in response to Seasailor

I turned off Spotlight (added all drives to privacy or using command line as suggested already) and ran the following:

/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.fram ework/Support/lsregister -kill -u -domain local -domain system -domain user -domain network

/System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.fram ework/Support/lsregister -kill -r -domain local -domain system -domain user -domain network

This immediately dropped the CPU usage from 100% down to almost 0%. So far it seems to have fixed my problems. Took a LOT of digging around to finally resolve this.

Reply