Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

CORESERVICESD takes 90%-100% CPU about 5 minutes after every fresh start

So, coreservicesd process takes 90-100% cpu after a fresh start. It doesn't start immediately after login but about 3-5 minutes after, and it happens +every time+ i start my computer and it lasts about 10 minutes or so before it stops eating the cpu.

I haven't figured out any way to stop this behavior. I've reset smc, emptyed /Library/Caches, clean installed Snow Leopard (without restoring from Time Machine backup) but nothing seems to help.

Does anyone here know what to do in my situation or does anyone have any new ideas what should I try to do? I appreciate every response.

MacBook Pro (unibody, late 2008), Mac OS X (10.6.2), Wireless Aluminium Keyboard + Mighty Mouse + 22" external display

Posted on Mar 7, 2010 3:25 AM

Reply
8 replies

Mar 7, 2010 4:14 AM in response to sarukuku

The whole console log for today is here: http://www.inexorable.me/Console_log.html

The repeating line with error:

"com.apple.launchd.peruser.501[126] Sun Mar 7 00:08:11 Joonas-Salovaaras-MacBook-Pro.local quicklookd32[4830] <Error>: CGImageDestinationFinalize image destination does not have enough images

7.3.2010 0.08.11 quicklookd32[4830] CGImageDestinationFinalize failed for output type 'public.tiff'"

With my knowledge I can only say that there is something wrong with QuickLook. Good questions might be why it is running quicklookd32 when I'm running my system in 64 bit mode (boot with 6 + 4 or make a permanent change to boot file as I've done) and what is the "public.tiff"?

Mar 7, 2010 4:36 AM in response to sarukuku

I tried doing a google search, but nothing obvious came up. Why are you running in 64-bit mode? If I remember correctly from what I read when SL first came out, unless you have some special software requirements or you are on an Xserv, you should allow your Mac to boot into standard 32-bit mode and allow SL to invoke 64-bit mode on a per application basis. Perhaps that's your problem. Try running in 32-bit mode for a while and see if the problem goes away.

Mar 7, 2010 4:44 AM in response to sarukuku

I suppose you know the beachballing problem on macs? Well I had it in 32 bit mode and it also was extremely annoying. Tried everything I could find from google, nothing helped except using the machine in the 64 bit mode. No beachballing of any kind after that. It wouldn't be nice to go back to that, it's even more annoying than this coreservicesd hang, but of course I can try if this specific error goes away.. I'll report back what the console says after fresh start in 32 bit mode.

Mar 7, 2010 5:18 AM in response to sarukuku

OK, I'll do that from now on. Booting to 32 permanently again. I've used my computer in 32 bit mode now for 20 minutes or so. No beachballing yet!

But lets get back to the coreservicesd thing. It fired up again after five minutes of waiting and just staring the Activity Monitor. After the 10 minute munching coreservicesd calms down and I collect the data from the Console log, it's here:
http://www.inexorable.me/Console_log32.html

Again, with my knowledge I can't find anything which would point to coreservicesd in any way? The former problem with the QuickLook and that strange .tiff is gone though. Good.

Any suggestions what to do now? Should I just call to support?

Mar 9, 2010 2:24 AM in response to sarukuku

OK folks, problem solved. At least mine is. No coreservcesd eating cpu anymore! Hurray! This is the second time I boot and the computer seems to run perfectly. If the coreservicesd problem comes back I'll report here.

So, what did I do:
1. Changed from 64 bit kernel + extensions to 32 bit.
2. Uninstalled SpiceRack and MozyHome Backup preference panes.
3. Repaired Premissions
4. Cleaned User Cache
5. Cleaned System Cache
6. Cleaned All Users Cache
7. Rebuilt Launch Services
8. Forced Empty Trash
9. Removed Corrupt Preferences
10. Updated Prebindings
11. Reindexed Spotlight
12. Cleaned Archived Logs
13. Cleaned All Logs
14. Flushed DNS Cache
15. Removed .DS_Store Files
16. Cleaned All Browser Caches
17. Updated Whatis Database
18. Updated Locate Database
19. Cleaned Font Caches
20. Booted from SL install dvd and ran Disk Utility's repaid disk & repair premissions.

After these operations my mac runs faster and all errors in the Console log are gone! All steps (except 1, 2 and 20) can be preformed with different maintenance apps. I used an app called MainMenu.

Message was edited by: sarukuku (fixed some spelling errors)

CORESERVICESD takes 90%-100% CPU about 5 minutes after every fresh start

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.