weird crashing problem

danix · Post by **danix** » Tue Jan 15, 2008 6:58 pm

I know that I should file a bug report, but I went to the trac site and it wasn't working.

I'm running Leopard on a MBP with the latest 10.5.1.
Over the weekend, my laptop started acting really weird and hanging. Existing apps will work, but trying to launch new apps results in a bouncing dock icon, then nothing. After rebooting, I would often see a blue screen, scrolling wheel, blue screen, etc.

After rebooting in safe mode and rebooting again, the system would come up.

One problem is that I was launching skype, adium and firefox at login. I disabled these, and was able to log in OK.

Starting Adium causes this behavior to start again. I've deleted adium, emptied trash, rebooted, and reinstalled, and the behavior returns.

From my console log, this is all I see that is unusual. No adium crash was reported recently:

1/14/08 12:29:21 PM com.apple.launchd[1] (0x10d2a0.mdworker) Failed to check-in!
1/14/08 12:29:21 PM com.apple.launchd[1] (com.apple.loginwindow[1095]) Exited abnormally: Abort trap
1/14/08 12:29:21 PM com.apple.launchd[1] (com.apple.loginwindow) Throttling respawn: Will start in 8 seconds
1/14/08 12:29:21 PM com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[1100]) Exited: Terminated
1/14/08 12:29:25 PM com.apple.launchd[1] (0x10d2a0.mdworker[1101]) Exited abnormally: Abort trap
1/14/08 12:29:25 PM com.apple.launchd[1] (0x10d2a0.mdworker) Failed to check-in!
1/14/08 12:29:28 PM com.apple.launchd[1] (com.apple.UserNotificationCenter[1103]) Exited abnormally: Abort trap
1/14/08 12:29:28 PM com.apple.launchd[1] (com.apple.UserNotificationCenter) Throttling respawn: Will start in 9 seconds
1/14/08 12:29:31 PM com.apple.launchd[1] (0x10c950.mdworker[1106]) Exited abnormally: Abort trap
1/14/08 12:29:31 PM com.apple.launchd[1] (0x10c950.mdworker) Failed to check-in!
1/14/08 12:29:31 PM com.apple.launchd[1] (com.apple.loginwindow[1104]) Exited abnormally: Abort trap
1/14/08 12:29:31 PM com.apple.launchd[1] (com.apple.loginwindow) Throttling respawn: Will start in 9 seconds
1/14/08 12:29:31 PM com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[1109]) Exited: Terminated
1/14/08 12:29:36 PM com.apple.launchd[1] (0x10d2a0.mdworker[1110]) Exited abnormally: Abort trap
1/14/08 12:29:36 PM com.apple.launchd[1] (0x10d2a0.mdworker) Failed to check-in!
1/14/08 12:29:38 PM com.apple.launchd[1] (com.apple.UserNotificationCenter[1112]) Exited abnormally: Abort trap
1/14/08 12:29:38 PM com.apple.launchd[1] (com.apple.UserNotificationCenter) Throttling respawn: Will start in 9 seconds
1/14/08 12:29:40 PM com.apple.launchd[1] (0x10d2a0.mdworker[1113]) Exited abnormally: Abort trap
1/14/08 12:29:40 PM com.apple.launchd[1] (0x10d2a0.mdworker) Failed to check-in!
1/14/08 12:29:42 PM com.apple.launchd[1] (com.apple.loginwindow[1114]) Exited abnormally: Abort trap
1/14/08 12:29:42 PM com.apple.launchd[1] (com.apple.loginwindow) Throttling respawn: Will start in 9 seconds
1/14/08 12:29:42 PM com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[1118]) Exited: Terminated
1/14/08 12:29:45 PM com.apple.launchd[1] (0x10d2a0.mdworker[1119]) Exited abnormally: Abort trap
1/14/08 12:29:45 PM com.apple.launchd[1] (0x10d2a0.mdworker) Failed to check-in!
1/14/08 12:29:49 PM com.apple.launchd[1] (com.apple.UserNotificationCenter[1120]) Exited abnormally: Abort trap
1/14/08 12:29:49 PM com.apple.launchd[1] (com.apple.UserNotificationCenter) Throttling respawn: Will start in 9 seconds
1/14/08 12:29:50 PM com.apple.launchd[1] (0x10d2a0.mdworker[1122]) Exited abnormally: Abort trap
1/14/08 12:29:50 PM com.apple.launchd[1] (0x10d2a0.mdworker) Failed to check-in!

So, any suggestions on where to look? I don't want to ditch adium but at this point I've had to resort to a spare laptop so I can keep working normally.

Thanks.

Balzorosso · Post by **Balzorosso** » Tue Jan 15, 2008 10:08 pm

Exactly same Machine, same OS, with same problem, with same sys profiler log.

Today my mac crashed again. No message from the OS, nor at the reboot. It just stops and the screen freezes. Game over.

danix · Post by **danix** » Thu Jan 17, 2008 11:52 pm

Well, I can say it's probably not adium. I switched to iChat for two days, and then suddenly Camino hung, causing the exact same behavior.

My mac buddy recommends an archive and reinstall, so that's what I'll do.

Post by **Catfish_Man** » Fri Jan 18, 2008 12:07 am

mdworker is spotlight's indexing process

danix · Post by **danix** » Fri Jan 18, 2008 12:33 am

I'm still working in crippled mode as I can't reboot right now. finder stopped responding, so I restarted it, but it can't start up.

Posting the system log just as interest, again, this has nothing to do with adium per se.

bash-3.2# tail system.log
Jan 17 16:31:19 tattoine /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[60580]: SessionGetInfo(0xffffffff) -> Mach 1102
Jan 17 16:31:19 tattoine /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[60580]: GetOurLSSessionIDInit(), returned error 0xe2, securitySessionID=0x0 attrs=0 uid=501 euid=501. cf Radar 5123589.
Jan 17 16:31:19 tattoine /System/Library/CoreServices/coreservicesd[60]: Client must provide a valid sessionID but passed 0, 0x0/0x0 version=10500000 uid=501 euid=501. cf Radar 5123589.
Jan 17 16:31:19 tattoine /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[60580]: LaunchServices/5123589: coreservicesd is running an unsupported version, 0 ( we are 10500000 ), so we cannot talk to it.
Jan 17 16:31:19 tattoine /System/Library/CoreServices/coreservicesd[60]: Client must provide a valid sessionID but passed 0, 0x0/0x0 version=10500000 uid=501 euid=501. cf Radar 5123589.
Jan 17 16:31:19 tattoine /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[60580]: LaunchServices/5123589: coreservicesd is running an unsupported version, 0 ( we are 10500000 ), so we cannot talk to it.
Jan 17 16:31:21 tattoine /System/Library/CoreServices/UserNotificationCenter.app/Contents/MacOS/UserNotificationCenter[60584]: SessionGetInfo(0xffffffff) -> Mach 1102
Jan 17 16:31:21 tattoine /System/Library/CoreServices/UserNotificationCenter.app/Contents/MacOS/UserNotificationCenter[60584]: GetOurLSSessionIDInit(), returned error 0xe2, securitySessionID=0x0 attrs=0 uid=501 euid=501. cf Radar 5123589.
Jan 17 16:31:21 tattoine /System/Library/CoreServices/coreservicesd[60]: Client must provide a valid sessionID but passed 0, 0x0/0x0 version=10500000 uid=501 euid=501. cf Radar 5123589.
Jan 17 16:31:21 tattoine /System/Library/CoreServices/UserNotificationCenter.app/Contents/MacOS/UserNotificationCenter[60584]: LaunchServices/5123589: coreservicesd is running an unsupported version, 0 ( we are 10500000 ), so we cannot talk to it.

Post by **Catfish_Man** » Fri Jan 18, 2008 12:39 am

Wow. Your system is really messed up. I've never seen people explicitly referencing bug reports in their console logs before (radar is apple's bug tracker).

danix · Post by **danix** » Fri Jan 18, 2008 1:27 am

Tell me about it. And to think I got a Mac so I wouldn't have to debug things like this...

Balzorosso · Post by **Balzorosso** » Tue Jan 22, 2008 4:26 pm

Two days ago, after 4 crashes in about half an hour, I stop using Adium. Everything is ok now.

To me, there must be something wrong with OSX 10.5 because with Tiger I always used Adium and it worked flawlessy.

Post by **evands** » Tue Jan 22, 2008 7:16 pm

Balzorosso, please report your problem(s) as explained at http://adiumx.com/faq/ReportingBugs and we'll be happy to take a look

danix · Post by **danix** » Tue Jan 22, 2008 8:34 pm

Final update - did an archive and reinstall, and it's happy with Adium (and Camino) again.