I just installed Leopard, but now every now and then the CPU use goes up to 190% with a process called DirectoryServices. Forgive my ignorance but what's going on? Applications don't work after a few seconds and all I am left to do is force shut down the computer and re-start. Any help is greatly appreciated!
Gabriel
That's just weird as I've installed 10.5 to a blank hard-drive, no upgrade nothing on the drive before.
We can rule out installation method basically then.
The "hack" where you set the Search Policy in "Directory Utilities" seems to have helped me though.
after the fresh install I've never rebooted the MBP again. It seems faster and more reliable than
before the upgrade.
Switched from airport (many wifis) to ethernet a lot of times, DirectoryService is no more wasting cpu.
My current uptime is 3 days, hope it'll get to 30 days! I hate rebooting my Mac.
This is not a solution to the problem, but an interesting observation nevertheless:
I've had the 190% problem almost ALL the time lately, especially when I've been offline - Until I uninstalled/stopped the "EarthDesk" (
http://www.macupdate.com/info.php/id/7492/earthdesk) application that I had running as default from boot.
Now 2-3 days later and so far no DirectoryService at 190%..
I archive and installed but still have the same problem return. In Tiger this never happened. Seems to happen when I have eye tv running for more than 2 hours.
After the fresh install, and with a small set of applications installed (which are declared to be Leopard-compatible), I've reached 7 days of runtime. Still going!
I was having this problem also - Mac Mini 2.0, factory-installed 10.4 upgraded to 10.5 then Software Update to 10.5.1, running EyeTV, TVShows, Transmission, Sofa Control and EarthDesk - happening pretty much every day.
Following suggestions in this thread, I ran a Repair Permissions about five days ago (using Disk Utility - no manual messing around with chmod), and the problem has not reappeared. I did have a kernel panic (a couple of days after the repair perms), but that was associated with Airport. Disk Utility didn't seem to list the same files/directories as being repaired that some have reported, so perhaps the reason some have not had luck with chmod is that they've missed some different files that Disk Utility will pick up. Worth a try, anyway - it's worked like a dream here.
Same issue here, only never above 100% cpu (core2duo macbook pro, 10.5.1). Temporarily solution is force quitting directoryservice in the activity monitor, re-executes itself and stays at 0% for a while...
It is not nice having to check my system health in the activity monitor every time my fan starts blowing!
I am sorry to hear all of you are having problems. I don't often suggest this, but as this is a user forum (that is users get helped by other users and not apple ) Have you all called apple? You have 90 days phone support with your purchase of leopard (more probably if you have apple care) and I would also use this link
http://www.apple.com/feedback/macosx.html That way Apple gets made aware of the problem and elevates it to the next level. And when I say all I mean everyone, sounds like this is a definite bug, and "the squeaky wheel gets the oil"
Good Luck
I've tried force quitting DirectoryService, but my computer will often completely lock up after doing that. I think it worked the first few times that I had this problem, but now all it does is freeze Leopard.
I also have this problem, but this problem only happens when I'm not connected to internet.
If there is not internet connection then directoryservice goes to 190% activity and the system hangs up. Has any one a solution to this? how can I address this problem to apple so they can help me?
Hi Guys !!
It seems to be that really earthdesk.dmg is the main cause for this problem. I de-installed it and after that Leo seems to work in a quiet way. I think that the problem is given in searching some information in the net. As you know, earthdesk try to connect a ftp server for the actualisation of the clouds. If no connection is given, it start in a loop and relaunched the loop so long, till cpu usage is on 196% or more. Same problem is given if you are using airport with no connection to the outside. After a lot of time that the computer is not working, usage of cpu will arrive at approx. 197% with no choice to do anything. The only solution is force power down the computer. I stay tuned to solve the problem, because i think it is mainly a "lookup" question for a deamon that starts (together with the DirectoryServices).