kext cache running CPU at 100%

Question

Level 4

3,605 points

kext cache running CPU at 100%

This has happened a few times now since upgrading to leopard. I just finished using Software Update to install a couple of things (no reboot required), after which I noticed the system running fast. Launched Activity Monitor to see that something called 'kextcache' using almost 100% CPU. I don't know what this is or why it suddenly feels the need to hog my system resources, but I have to force quit it in order to bring things under control again (doesn't seem to affect anything when I do). Can anyone tell me what this is, why it should be doing what it's doing, and how I can stop having to force quit it?

iMac G5 20", 2.1GHz, 250GB HD, 1.5GB ram, iBook G4 1.33Ghz,, Mac OS X (10.5.2), Maxtor 200GB onetouch III, 6mb DSL, Linksys WRT54G, iPod Classic 80Gb, Nano 2G

Posted on Feb 22, 2008 12:10 PM

Reply

Answer 1

Kappy

Level 10

362,007 points

Feb 22, 2008 12:16 PM in response to Simon-UK-

It's a rebuild of the extensions cache OS X creates in order to improve startup and operational speed. Killing the process won't do much because the system will simply attempt to rebuild the cache again.

Now, if there's some problem with your drive and the file cannot be saved that may cause some problem as might a pre-existing corrupted cache. You can use a tool like TinkerTool System to remove all user and system caches which will force them to be rebuilt upon restart. This should fix any problems associated with them.

Reply

Answer 2

Feb 22, 2008 12:18 PM in response to Simon-UK-

A brief summary from the man page for kextcache:

The kextcache program creates or updates kext caches, which are used to speed up kext loading operations and to prepare kexts for inclusion in such media as device ROM. It is invoked automat-ically as needed to rebuild the system caches, and can be used manually to build kext archives to be stored in device ROM.

Something isn't quite right. Open the Console.app and look for error messages in the system.log involving kextcache. If you post them someone might have an answer.

Reply

Answer 3

Simon-UK- Author

Level 4

3,605 points

Feb 23, 2008 12:42 AM in response to Kappy

Thanks for the suggestions guys. I've removed all cache files, and hopefully that will solve the problem. Will post back if problem persists.

Reply