Currently Being ModeratedMay 28, 2013 11:21 PM (in response to Kevin Stanchfield)
Kevin, I'm not sure you know what you are talking about (but I know I don't haha).
I don't think ti is a simple memory error, as then why would it consume the harddrive space? My two week old macbook air had this problem and the only thing I installed was Microdoft Office, and the only things i dowloaded were a few very small pdf, powerpoint, and word documents.
When the problem occured, after a few hours of stressful panic i decided to try to restrt the computer. Unfortunately I couldn't save any of my documents first because there was no room on the harddrive. After restart, 100 GB magicaly reappeared.
This is pretty crap, especially as half the reason I bought this rediculously expensive computer was so I didn't have to spend all my time trying to make my computer work properly as i did with my previous Vista computer.
Currently Being ModeratedMay 28, 2013 11:58 PM (in response to chapplie)
Most operating systems (including OS X) will start using the hard drive when RAM is used up. This happens when you either don't have enough RAM, or a rogue process takes it all. This also slows down your computer big time.
Either way, Activity Monitor will tell you wich process is the culprit.
Currently Being ModeratedMay 29, 2013 1:03 AM (in response to Kevin Stanchfield)
If I remember correctly the answer was "kernel_task", whatever that is, which I only found by selecting "all processes" instead of the default "my processes"
Currently Being ModeratedMay 29, 2013 1:58 AM (in response to chapplie)
You're the first person to report an issue with kernel_task here. What version of OS X are you using? How much "Real Mem" did Activity Mon say kernel_task was using? Post a screenshot if you can.
Currently Being ModeratedMay 29, 2013 6:18 AM (in response to chapplie)
kernel_task always takes a lot of memory which I *THINK* can be released to the system if other apps need more memory, so even though it may have been the first in your process list, it may not have been the culprit. Can you remember roughly how much memory it was using?
Currently Being ModeratedMay 29, 2013 8:31 AM (in response to Whee)
Currently Being ModeratedMay 29, 2013 8:42 AM (in response to Csound1)
Currently Being ModeratedMay 29, 2013 8:46 AM (in response to Csound1)
I disagree with you disagreeing.
With most apps using less than 200mb, kernel_task using 650mb in comparison is a lot. It will often be at the top of the list for memory usage. Yet, it is completely normal.
Currently Being ModeratedMay 29, 2013 8:49 AM (in response to Whee)
What is your Page Out number?
Currently Being ModeratedMay 29, 2013 8:56 AM (in response to Whee)
Your Mac has needed to swap 1.6mb to disk since you last restarted. That is not a problem: memory is being used effectively on your Mac. If you want to get that down to Zero add more Ram.
Currently Being ModeratedMay 29, 2013 9:43 AM (in response to Whee)
650mb is not alot - and clearly not enough to cause a system with gigabytes of RAM to start swapping out to disk. Check out the screen shot from a user above who's Safari process was using almost 6gb of RAM - THATS a lot. For me, it was an HP printer driver that was consuming GB of RAM, slowing down my parents computer.
Currently Being ModeratedMay 29, 2013 11:00 AM (in response to Andrew_OB)
After isolating Firefox (I suspect it was an addon or specific website Java scripts) I have found Sophos AV consume huge memory (any amount of free disk space can be used up) when doing a full system scan. The only alternative I have found is to stop the scan and run it some other time - and if I am lucky the full scan goes through.
Currently Being ModeratedMay 29, 2013 1:40 PM (in response to Kevin Stanchfield)
Read what I said again and read it in its context.
The guy suspected kernel_task to be the culprit because it's what was using the most RAM.
kernel_task being the process that uses the most RAM is not suprising, because most apps (or I should say "processes") use less than 200MB and compared to most apps, which use less than 200MB, 650MB is a lot. It's especially "a lot" considering that over 80% of processes use less than 100MB. And my point was that even if it used a lot of RAM relative to the other processes, that doesn't make it the culprit.
I'm not saying "650mb is a lot for kernel_task" or even "650mb is a lot relative to total RAM", I'm saying "650mb is a lot compared to most processes" and that it's not uncommon for it to be the process that uses the most RAM. Again, read again.