|Mar 4, 2012, 02:40 PM||#1|
Locationd Taking 95% CPU constantly in ML
I've had ML on my iMac 7,1 since release. This last week or so, locationd keeps running every few minutes and taking 95% of CPU.
I've tried turning off all Location Services in ML, including Find My Mac and Sending Apple Diagnostics, and it has had no affect whatsoever.
What the heck is going? Why would this start happening? Why is Apple siphoning location data from me without my consent? And why is it running constantly?
|Mar 4, 2012, 04:56 PM||#4|
Weird that it should be using so much CPU, you might want to grab a profile of it using Activity Monitor and submit it to Apple via bugreport.apple.com, let them know you're having trouble so they make sure to fix it.
What happens when you just kill the process?
"Early 2008" MacPro, 2 x 3.2ghz Quad-Core Xeons, 10gb DDR2 800mhz ECC RAM, 120gb Solid State Drive (Mac & Windows OS), 4 x 750gb hard-drives (striped, users/files), NVidia GeForce 8800GT (512mb).
|Mar 5, 2012, 05:22 PM||#6|
|Thread Tools||Search this Thread|
|thread||Thread Starter||Forum||Replies||Last Post|
|All We Know About Maximizing CPU Related Performance||Tutor||Mac Pro||1017||Apr 10, 2014 01:30 PM|
|ruby process running in background, taking 100% cpu||zentenk||MacBook Pro||1||Nov 9, 2011 12:46 PM|
|Dashboard Client taking ~3-4% CPU constantly while idle?||Bottomsup||OS X||1||May 28, 2011 09:48 PM|
|Dashboard client takes up 99.8% of CPU constantly.||BJB Productions||Mac Basics and Help||3||Jul 2, 2010 09:26 PM|
|XP home at 95% CPU even when idle. wtf?||shecky||Windows, Linux & Others on the Mac||7||Oct 16, 2007 10:16 PM|
All times are GMT -5. The time now is 05:19 PM.