MacBook Crash

My MacBook Pro shall henceforth be known as MacBook Crash.

Since “upgrading” to Leopard, I’m suffering intermittent but incredibly annoying lock-ups. The symptoms are that the processor usage goes up to 200% (both CPUs maxed out). I see that DirectoryService is always the culprit, assuming Activity Monitor was running beforehand. As far as I can tell, it’s always when I’m offline.

DirectoryService

More often than not, before I’m able to take remedial action (like killing the process), the machine goes into terminal decline. Anything that wants to read from or write to disk will hang, and the only answer is a hard reboot.

According to the Apple forums I’m not the only one with the problem, and there’s even a proposed solution. Sadly this doesn’t appear to have fixed the problem in my case, as I had my first hard crash since trying the fix on Friday (after the last hard crash).

At this point I’d seriously consider reverting to Mac OS X 10.4, if it wasn’t such a pain to do a nuke and reinstall. Although Spotlight didn’t work and there was no Time Machine or Spaces, it did at least have the virtue of being pretty stable.

Is anyone else having the same problem?

This entry was posted in Planet and tagged , , , . Bookmark the permalink.

2 Responses to MacBook Crash

  1. Adrian Bool says:

    Leopard is doing me OK for me so far on a lowly MacBook. Have you joined your machine to a Domain or anything similar? If its just occurring when you’re offline, I guess it maybe some silliness about it not being able to reach the DNS server. Mmm. hostnames.

    Within System Preferences, Sharing I guess you have a Computer name set? Mine is widow (*black* MacBook). Put your computer name into /etc/hosts – on the same line as localhost,

    127.0.0.1 localhost widow

    Also, place the same name in /etc/hostconfig,

    HOSTNAME=widow

    Give your machine a reboot and she if she hangs together any better!

  2. stega says:

    Yes.

    One weekend I put Leopard on four of my five Macs. Three were fresh installs and went fine, the last one was an upgrade and quite a nightmare. Frequent crashes and enough issues that in the end, I moved all my data files off the startup disk (mainly everything in ~) and then did a fresh install. I haven’t had an issue since. The Tiger install was over 2 years old and there was quite a lot of crap just laying around–even Agent Smith agreed it was probably wiser given how many tweaks and customized items to just wipe and redo.