Kernel_task hogs ram... which kexts can I delete/what else can I do?

[wyager]

This is pretty ridiculous... kernel_task is hogging upwards of 540 megabytes of RAM, on top of the gigabyte of RAM already "wired" for OS use. Almost half of my RAM is non-usable. I hear that a gig of wired memory in 10.6 is normal, but not this much memory used by kernel_task.

Running "Consultant's Canary" turns up the following kexts (I assume it only reports third-party kexts, as it seems to ignore all apple kexts).

 Accusys6xxxx.kext                             com.Accusys.driver.Acxxx
   BJUSBLoad.kext                                jp.co.canon.bj.print.BJUSBLoad
   CalDigitHDProDrv.kext                         com.CalDigit.driver.HDPro
   EPSONUSBPrintClass.kext                       com.epson.print.kext.USBPrintClass
   FTDIUSBSerialDriver.kext                      com.FTDI.driver.FTDIUSBSerialDriver
   HighPointIOP.kext                             com.highpoint-tech.kext.HighPointIOP
   HighPointRR.kext                              com.highpoint-tech.kext.HighPointRR
   hp_designjet_series.kext                      com.hp.print.hpio.Designjet.kext
   hp_Deskjet_io_enabler.kext                    com.hp.print.hpio.Deskjet.kext
   hp_fax_io.kext                                com.hp.kext.hp-fax-io
   hp_Inkjet1_io_enabler.kext                    com.hp.print.hpio.Inkjet1.kext
   hp_Inkjet2_io_enabler.kext                    com.hp.print.hpio.Inkjet2.kext
   hp_Inkjet3_io_enabler.kext                    com.hp.print.hpio.Inkjet3.kext
   hp_Inkjet4_io_enabler.kext                    com.hp.print.hpio.Inkjet4.kext
   hp_Inkjet5_io_enabler.kext                    com.hp.print.hpio.Inkjet5.kext
   hp_Inkjet7_io_enabler.kext                    com.hp.print.hpio.inkjet7.kext
   hp_Inkjet8_io_enabler.kext                    com.hp.print.hpio.inkjet8.kext
   hp_Inkjet9_io_enabler.kext                    com.hp.print.hpio.Inkjet9.kext
   hp_Inkjet_io_enabler.kext                     com.hp.print.hpio.Inkjet.kext
   hp_io_printerclassdriver_enabler.kext         com.hp.hpio.hp_io_printerclassdriver_enabler
   hp_Laserjet_io_enabler.kext                   com.hp.print.hpio.Laserjet.kext
   hp_Officejet_io_enabler.kext                  com.hp.print.hpio.Officejet.kext
   hp_Photosmart_io_enabler.kext                 com.hp.print.hpio.Photosmart.kext
   hp_PhotosmartPro_io_enabler.kext              com.hp.print.hpio.PhotosmartPro.kext
   hp_psa640_io_enabler.kext                     com.hp.hpio.hp_psa640_io_enabler
   hp_qc_io_enabler.kext                         com.hp.hpio.hp_psa530_630_io_enabler

I have no idea what half of these are, so I'm afraid to delete them. HP seems to be running an inordinate number of extensions... I did read something about the Accusys text being related to RAID, which is strange in my single-hard-drive macbook... The only kext I know for a fact that I use is FTDIUSBSerialDriver.kext. Can I just go ahead and delete all of the ones I don't recognize? I'm not actually sure which of these are even taking up all of the memory... is there any way to look at which kexts are being so demanding?


Additionally, is there any way to reduce the amount of wired memory?

Thanks!

 

[chscag]

How much overall memory do you have? Kernel extensions that are not actively being used do not absorb large amounts of memory. In any event I would not remove any kernel extensions regardless if they are not being used or active. The HP kernel extensions are for printers.

 

[wyager]

How much overall memory do you have? Kernel extensions that are not actively being used do not absorb large amounts of memory. In any event I would not remove any kernel extensions regardless if they are not being used or active. The HP kernel extensions are for printers.

4 Gigs. How do I check which kernel extensions are currently in use? Because something is taking up WAY too much RAM.


And why does HP need so many extensions? Can't they get their act together and make a universal one?

 

[chscag]

You can get a good picture of what's using memory by opening your "Activity Monitor.app" from Applications, Utilities. Take a look at what processes are running and how much memory is allocated to each.

As far as the HP kernel extensions, that's not unusual as they're different for each printer. The problem (and I have the same thing going on as you do) is that if you have an HP printer, Apple will provide the entire series of printer drivers and kernel extensions during an update or initial install.

I also have a Canon printer and it's the same. Personally, I wouldn't worry about it. You have enough memory with 4 GB for running most things. If you're into graphic design or Cad work, you may want to boost the memory.

 

[vansmith]

The last thing you want to do is start messing with kexts - you're asking for trouble by doing that. Also note that kexts aren't active unless they've been loaded. To check which kexts are loaded, open up Terminal (/Applications/Utilities) and execute the following:

kextstat -l

I'm willing to bet that a significant portion of them are Apple ones.

 

[wyager]

@chscag
Activity monitor is useless for checking which kexts are hogging the ram. It only shows processes that the user "should" interfere with.

The last thing you want to do is start messing with kexts - you're asking for trouble by doing that. Also note that kexts aren't active unless they've been loaded. To check which kexts are loaded, open up Terminal (/Applications/Utilities) and execute the following:

kextstat -l

I'm willing to bet that a significant portion of them are Apple ones.

Thanks! That's what I wanted.

LOL-

com.apple.Dont_Steal_Mac_OS_X

.

Subtle.


You are right, everything running is an apple kext. This does not explain why over an eighth of my RAM is now being thrown away on top of the fourth already used by the OS.

The biggest culprits are com.apple.kext.ATISupport and com.apple.ATIRadeonX3000, but together they only use only 3.8 megs of RAM (0x11b000+0x297000 bytes). ***?

The OS is now using 1.8 gigs of RAM total.

 

[BrianLachoreVPI]

LOL-

com.apple.Dont_Steal_Mac_OS_X

.

Subtle

LOL - Hmmmm - I don't have that kext loaded. Maybe Apple trusts me more?

 

[wyager]

LOL - Hmmmm - I don't have that kext loaded. Maybe Apple trusts me more?

Ha, maybe Apple forgot to add the new MBPs to the "approved" list.

 

[vansmith]

LOL - Hmmmm - I don't have that kext loaded. Maybe Apple trusts me more?

Are you running a PPC version of OS X? See here for more info.

wyager: When was the last time you restarted? Restart the machine, leave it alone and see if kernel_task starts consuming more and more memory.

 

[BrianLachoreVPI]

Are you running a PPC version of OS X? See here for more info.

I sure hope not. No - I have one of the newer MBPs updated to 10.6.7. Ok - I just looked again - and this time I see it - maybe I just missed it.

 

[wyager]

wyager: When was the last time you restarted? Restart the machine, leave it alone and see if kernel_task starts consuming more and more memory.

When I restart, it takes up 385 megs of RAM. Three minutes later, it's up to 410 megs. It seems to stabilize for periods then go up again.