You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

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

kernel_task consumes a lot of RAM in early 2011 MBP, sometimes Finder too

Hi,

My old MBP3,1 (late 2007, 2.4 GHz Core 2 Duo) worked quite well with 4 GB of RAM, even after weeks without restarting. In fact, I used all available RAM only on some larger analyses using R, which loads the entire dataset in memory. To be able to run these few analyses faster on my new machine (early 2011 MBP), I bought the 8 GB RAM option.

In Activity Monitor, I noticed something strange. Whereas my old MBP shows kernel_taks as using between 100 and 200 MB of RAM, the new MBP uses about 550 MB just after the machine started up and often shows over 600 after a few hours or days of use. A one year old iMac, again Core 2 Duo with 4 GB of RAM, gives a kernel_task memory usage below 200 MB after weeks of use.

I've not been able to find what kernel_task does. Is this amount (around 600 MB, but it has gone up to 800) normal? Is it managiing the additional number of cores that requires this behind the scenes amount of RAM?

Anyway, I now quite often have more than 4 GB of RAM in use even when I have only a few applications running (not even including R!), which surprises me.

Also today, after moving a lot of files back and forth between an external drive and the new MBP, after emptying the garbage can that contained a hefty number of files and doing a first Time Machine backup, the Finder ended up using 2,4 GB of RAM according to Activity Monitor. I have never seen anything like this (although I admit not having Activity Monitor on all the time). Even after the backup was finished and the external drive disconnected (in fact the machine was left idling for a few hours) cpu usage was down to nearly zero, the Finder kept its 2.4 GB of RAM. I restarted and the new RAM usage for the Finder was 26 MB. I have a screen shot showing the 2.4 GB, but I could not find a way to attach it to this message. I can send it by email on request. I don't think this Finder behavior was normal.

Somewhat worried,

Denis

MacBook Pro 2.2 GHz i7, 8 GB RAM, Mac OS X (10.6.6)

Posted on Mar 16, 2011 12:04 AM

Reply
216 replies

Jan 14, 2012 4:40 PM in response to eww

Then move on to helping other people.


Hope Apple reads these forums and sees just how many people are having problems with their lovely OS needing 4GB of RAM to do its tasks. This makes it more of a resource hog than even Vista. If we get 16GB of RAM or even 1TB of RAM if it existed, the lovely OS will take 500GB of it. I'm sure this makes sense to you and allows you to maintain your super gracious manner.

Jan 14, 2012 5:02 PM in response to wyager

Thanks wyager. After a fresh boot, it's about 600MB. The 4GB is what it's running now. I booted last evening my time.


Based on some suggestions on these forums i downloaded "gfcardstatus" and let it run. Without it, the whole system was crashing (that gray screen with white text -- similar to windows blue screen -- that takes over and says please reboot), but at least it's not crashing now, but the overall experience is sluggish and the mouse cursor just hangs sometimes because it's so slow.


Because of my industry, I have to work with large video files. I wonder if the deleting/adding/deleting of lage video files (over 6GB or so each file) has defragmented my system? Or what? Why's it taking so much for the kernel_task?


Many thanks for any ideas..

Feb 8, 2012 7:38 AM in response to DChabot

Hi Guys - Newbie here. Recently switched from Quad core PC (4years old) 4G of RAM to a MBP i7 8G


Using Photoshop CS5, Lightroom, with half a dozen passive tabs open on Firefox, Itunes blasting out and..... nothing else. I'm often left with a DOZEN OR SO MEGS OF RAM!!!


Now, twenty years ago I'd be really happy with this but I'm now rather bored of that spinning wheel of death.


In truth - My Mac has been pretty stable but not much faster than my old PC. I expected more.


Paid £35 for an Apple support call (Yet I'm still in warranty)


Paid £35 petrol for a trip to Genius store in Manchester. The man smiled at me and said my Apple is perfect - It's obviously a software issue.


So guys.... It's a software issue. The MacPro seems to not like CS5 or Lightroom, or maybe even I-Tunes, or Firefox. (I've re-installed everything and followed Adobes best practices to the letter. Apart from putting my scratch discs on a seperate partition) - What does it like? Can it cope with word documents or spreadsheets?


Since returning from Genius, I've tried running aplications without CS5 and Lightroom. OK, now I have a whopping 3G of RAM left. Any idea why 5G of RAM is being eaten up by basic stuff?


If I'd have waited a few more weeks I could have bought a MBP with 16G of RAM. Sadly I'm maxed out at 8.


Apple support isn't helping. Honestly have no idea why Apple supporters are so loyal to the brand. (It looks dead sexy though)

Feb 8, 2012 9:03 AM in response to DChabot

So after around half an hour of activity. You'll see from the grabshot...


I've been working on one layered file. (Admittedly a large one with 20 layers)


Closed the file down.


Now cs5, Lightroom Firefox and Finder running.


1.57G free now. (used more than 6G RAM)


It seems that CS5 is hogging 2.3 G of RAM, even though the file was closed over ten minutes ago.


Anyone know why this memory stays Used even when programmes are idle? This normal?


User uploaded file

Feb 8, 2012 11:00 AM in response to dave1click

Dave, we feel your pain. However, you might be able to palliate the problem with photoshop memory usage.


There are several probable reasons that CS5 is using so much RAM, ranging from a problem on Adobe's end to a problem with the OS (which is certainly the case with Kernel_task).


I recommend installing the developer tools, and then running the "purge" command in the terminal. This command tells the kernel to dump all inactive memory, and might perform some garbage collection functions as well. I'm not really sure, because the man page is outdated, but the function works.


Objective-C (the language used to make most OS X applications) is not garbage-collected, and has weird memory management, so a lot of applications end up accidentally "using" a huge chunk of memory that they're not actually using. It's a little hard to explain, but if you're programming-oriented, you should be able to google search for more info.

Feb 8, 2012 1:40 PM in response to DChabot

I just want to update that I have upgraded to 16GB RAM on my 2011 MBP.


The kernel task now takes about 1.5GB RAM after reboot, which is again increased.


So I think Apple designed the kernal task to take certain amount of RAM depending on total available.


I don't know, I do not quite like this design and do not know the rationel behind it. I am sure kernel task do NOT need so much RAM to function. And it feels like a waste.

kernel_task consumes a lot of RAM in early 2011 MBP, sometimes Finder too

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