Je bedoelt Kernel_task, uiteraard. Welnu FF voor je verzameld:
What Is ‘kernel_task’ and Why Is It So RAM Hungry?
Every so often, I see MemoryStick reporting a lot of pageable RAM is being used. I checked out Activity Monitor and sorted by what was using the most memory. I found process 0 named kernel_task being run by root. It’s using little to no CPU at any given time, but has 36 threads and is using anywhere from 75 to 78 megabytes of real RAM and a little more than 745 megabytes of virtual RAM. The only thing I’ve been able to find by searching is old comments referencing certain HP drivers, USB ports, and OS X version 10.2.2. I don’t use any HP products, nothing is currently plugged into my USB ports, and I’m running OS X 10.3.2.
Please chime in if you know what’s going on here.
» Posted by ALBj at 09:42 PM (ET)
Category: Housekeeping, Mac
To the best of my knowledge, kernal_task is the kernel of your system (hence, process 0). It is the heart of your OS and is uber-important to the functioning of your system. Kernel extensions, like drivers to talk to printers, mice etc. are loaded wia kernel extensions. That’s why you found that old info. s Early in MacOS X’s days (!), badly behaved kernel extensions caused kernal panics (the Mac equivalent of the Blue Screen of Death). It is run as root because of it’s importance, and power - it IS your system’s heartbeat.
Any UNIX gurus should feel free to correct me here.
» Posted by Ryan
April 5, 2004 11:23 PM
Ahh yes, as Mac OS catches up with Windows, you will see this more and more. OSs use the kernel tasks to run things below the GUI to ensure the tasks get top priority and are harder to screw with. The downside is that if a kernel task has a bug, it can often take out your whole system. Windows has suffered with this for years and only recently has been able to drastically reduce this problem by reorganizing the way kernel operations are handled.
The other issue with this is that kernel tasks are often unnamed more or less because they are started by the OS itself and thus get labeled with a generic “kernel task” type of label. So unless the OS provides you with a driver diagnostics (All versions of Windows do), it can be very difficult to track down which driver is causing a certain problem.
The point to this story is, you are stuck with kernel tasks, and before too many more versions, you will start seeing other similiar “generic” OS labels in your task list. I’m not certain of what is available now, but one can only hope the the Unix/Linux crowd learns from Microsoft’s mistake and provides better kernel level diagnostic tools early on