Welcome to the MacNN Forums.

0157988944 · 05:49 PM

This has happened twice in the past week... Application after application freezes and then the whole thing is frozen, and requires a restart. It looks like there's not even any message about it in the console, but I suck at reading logs, so here is my system.log from after the crash:

seanc · Dec 30, 2008, 07:10 PM

I've had this happen once and I can't remember whether this was directly before or after one of my MacBooks keeled over or not.

Boot into Single User Mode (command + s after the chime) and run fsck -fy as prompted until it says OK, if it says reboot, do so and repeat the process until it says OK.
Make sure you have a current backup.

What new software or hardware have you installed recently? Double Command?

All your system log really shows me is the boot up process of your MacBook Pro.
You could get rid of your startup item entry for sleepwatcher since it apparently doesn't exist.

What's the console said before the freeze/issues?

0157988944 · Dec 30, 2008, 07:58 PM

The console hadn't said anything for an hour before the freeze. I have recently installed double command, it could be the issue.

0157988944 · Dec 30, 2008, 08:10 PM

And the HDD appears to be OK.

Big Mac · Dec 30, 2008, 08:16 PM

What's double command?

0157988944 · Dec 30, 2008, 08:17 PM

Lets you remap your keyboard. I use it to change the small enter key on my MBP keyboard to Option so it matches my BT Aluminum Keyboard.

Simon · Dec 31, 2008, 04:47 AM

Remove all the iStat stuff. I had similar issues with iStat Pro on my MBP a while ago.

People were experiencing freezes just because of a widget.

iStat is evil.

seanc · Dec 31, 2008, 08:44 AM

Really?

I saw iStat and throught EVERYBODY is using iStat, it can't be the cause of the problem...

Simon · Dec 31, 2008, 09:16 AM

I thought so too until I noticed that my freezes (I had suspected it was my 8600M GT) and wake form sleep issues stopped as soon as I got rid of all of the iStat crapola. Why their simple little stuff can raise so much havoc is beyond me. Fortunately everything iStat offers can be done with other tools.

0157988944 · Dec 31, 2008, 10:45 AM

No, I already HAD the iStat issues

These aren't the same ones.

seanc · Dec 31, 2008, 10:50 AM

Dec 30 17:49:00 MacBookPro SystemUIServer[152]: \n MenuCracker\n see http://sourceforge.net/projects/menucracker\n MenuCracker is now loaded. Ready to accept new menus. Ignore the failure message that follow.
Dec 30 17:49:01 MacBookPro SystemUIServer[152]: failed to load Menu Extra: NSBundle </Users/Adam/Library/Application Support/iStat menus/Extras/MenuCracker.menu> (loaded)
Dec 30 17:49:02 MacBookPro SystemUIServer[152]: MenuCracker: Loading 'iStatMenusTemps'.
Dec 30 17:49:07 MacBookPro SystemUIServer[152]: MenuCracker: Loading 'iStatMenusNetwork'.
Dec 30 17:49:08 MacBookPro SystemUIServer[152]: MenuCracker: Loading 'iStatMenusDateAndTimes'.

Looks like you have some residual iStat hanging around...

0157988944 · Dec 31, 2008, 10:52 AM

No, I have iStat. But I already had the iStat display issues. Which were HELPED by removing iStat but they still existed. So iStat somehow irritated the problem a lot, but it wasn't the root cause. After Apple replaced my Logic Board everything was dandy. Then I put iStat back.

Simon · Dec 31, 2008, 11:34 AM

And now the problems are back. What a coincidence.

0157988944 · Dec 31, 2008, 11:43 AM

This is a whole different thing, but I uninstalled istat just for kicks... we'll see.