Reply to thread

Message

<blockquote data-quote="wyager" data-source="post: 1220256" data-attributes="member: 195253">This is pretty ridiculous... kernel_task is hogging upwards of 540 megabytes of RAM, on top of the gigabyte of RAM already &quot;wired&quot; 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 &quot;Consultant's Canary&quot; turns up the following kexts (I assume it only reports third-party kexts, as it seems to ignore all apple kexts).[CODE]&nbsp;Accusys6xxxx.kext&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; com.Accusys.driver.Acxxx&nbsp;&nbsp; BJUSBLoad.kext&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; jp.co.canon.bj.print.BJUSBLoad&nbsp;&nbsp; CalDigitHDProDrv.kext&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; com.CalDigit.driver.HDPro&nbsp;&nbsp; EPSONUSBPrintClass.kext&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; com.epson.print.kext.USBPrintClass&nbsp;&nbsp; FTDIUSBSerialDriver.kext&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; com.FTDI.driver.FTDIUSBSerialDriver&nbsp;&nbsp; HighPointIOP.kext&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; com.highpoint-tech.kext.HighPointIOP&nbsp;&nbsp; HighPointRR.kext&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; com.highpoint-tech.kext.HighPointRR&nbsp;&nbsp; hp_designjet_series.kext&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; com.hp.print.hpio.Designjet.kext&nbsp;&nbsp; hp_Deskjet_io_enabler.kext&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; com.hp.print.hpio.Deskjet.kext&nbsp;&nbsp; hp_fax_io.kext&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; com.hp.kext.hp-fax-io&nbsp;&nbsp; hp_Inkjet1_io_enabler.kext&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; com.hp.print.hpio.Inkjet1.kext&nbsp;&nbsp; hp_Inkjet2_io_enabler.kext&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; com.hp.print.hpio.Inkjet2.kext&nbsp;&nbsp; hp_Inkjet3_io_enabler.kext&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; com.hp.print.hpio.Inkjet3.kext&nbsp;&nbsp; hp_Inkjet4_io_enabler.kext&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; com.hp.print.hpio.Inkjet4.kext&nbsp;&nbsp; hp_Inkjet5_io_enabler.kext&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; com.hp.print.hpio.Inkjet5.kext&nbsp;&nbsp; hp_Inkjet7_io_enabler.kext&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; com.hp.print.hpio.inkjet7.kext&nbsp;&nbsp; hp_Inkjet8_io_enabler.kext&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; com.hp.print.hpio.inkjet8.kext&nbsp;&nbsp; hp_Inkjet9_io_enabler.kext&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; com.hp.print.hpio.Inkjet9.kext&nbsp;&nbsp; hp_Inkjet_io_enabler.kext&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; com.hp.print.hpio.Inkjet.kext&nbsp;&nbsp; hp_io_printerclassdriver_enabler.kext&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; com.hp.hpio.hp_io_printerclassdriver_enabler&nbsp;&nbsp; hp_Laserjet_io_enabler.kext&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; com.hp.print.hpio.Laserjet.kext&nbsp;&nbsp; hp_Officejet_io_enabler.kext&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; com.hp.print.hpio.Officejet.kext&nbsp;&nbsp; hp_Photosmart_io_enabler.kext&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; com.hp.print.hpio.Photosmart.kext&nbsp;&nbsp; hp_PhotosmartPro_io_enabler.kext&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; com.hp.print.hpio.PhotosmartPro.kext&nbsp;&nbsp; hp_psa640_io_enabler.kext&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; com.hp.hpio.hp_psa640_io_enabler&nbsp;&nbsp; hp_qc_io_enabler.kext&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; com.hp.hpio.hp_psa530_630_io_enabler[/CODE]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!</blockquote>

[QUOTE="wyager, post: 1220256, member: 195253"] 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). [CODE] 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[/CODE] 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! [/QUOTE]

Verification

Name this item. 🍎