Currently Being ModeratedJan 7, 2012 7:10 PM (in response to Joasousa)
First, using the word "retard" as you did is offensive. Second, most people here would say that the fact that you work in IT would make it a virtual certainty that you don't know what you're doing. Don't come to these forums and throw around insulting terms while acting like you know everything. You DON'T know everything, or you wouldn't have to ask us!
If you are still interested in getting help here, you're going to need to be open to forgetting what you "know" is the problem and start listening to other ideas.
Currently Being ModeratedJan 8, 2012 9:04 AM (in response to thomas_r.)
Second, most people here would say that the fact that you work in IT would make it a virtual certainty that you don't know what you're doing.
And you are actually lecturing me about being offensive? This must me some sort of joke. Look at yourself before giving advice on how to behave in a forum.
To those who aren't so "sensitive" and who don't have some prejudice against the "ignorant IT guy", what I was trying to say it that sometimes you shouldn't assume that the other side doesn't know anything.
I don't know everything, you shouldn't assume that I know nothing. I researched, I read blog and foruns about how MacOS manages memory, I just wanted to see if more people had the same problem. If not, I probably had a hardware problem.
PS: I do want to know your explanation for the 5 GB of active memory (screenshot I posted) when I only have Safari open, and that application is only consuming about 300 MB of memory.
Currently Being ModeratedJan 8, 2012 9:15 AM (in response to Joasousa)
I wouldn't expect you to have gotten the humorous side to that statement, since it was a bit barbed and pointed at you. The point is that saying you work in IT gives you absolutely zero additional credibility, because nearly everyone here has had experience with IT folks who don't know what they're doing, and even those who do are not usually experts at low-level memory management. So you might as well say you're a barber or a mortician. If you were a systems engineer with expertise in memory management schemes, then that would be worth mentioning.
Your problem is poor performance. You have chosen to blame that on a memory-related bug in the OS. That is unlikely to be the case, but if you remain insistent that it is, nobody here can help you further. You will have to wait and hope for Apple to fix it. If you would prefer to try some troubleshooting to fix it on your own, you will need to be more cooperative. Though your use of "retard" as a perjorative term will likely prejudice some here aginst helping you, so you'll probably benefit from a brand new topic.
Currently Being ModeratedJan 8, 2012 9:31 AM (in response to thomas_r.)
I'm not insistent, I've given every information that requested except the real memory screenshot (and even that one I provided).
If you people stop helping someone because this person uses a term that you don't like (especially when used in reference to himself), then I should really find help someplace else.
And your analogy about the IT guy and comparing him to a mortician doesn't make any sense. From your perspective when a user complains about a problem with his computer the IT guy should tell him to call his memory expert system engineer. He should use your analogy and compare himself to the mortician. He would probably get fired but hey, he's not a systems engineer so he must be ignorant.
Currently Being ModeratedJan 24, 2012 4:37 PM (in response to Joel Bruner1)
Thank you for reminding me of that X11 command (purge). I had already forgotten it was there (or that I had actually installed X11 long ago when I was still on SL).
I have 12GB of RAM installed. I don't run into this inactive memory problem very often but I do sometimes. I don't have a real memory problem. RM usage is ok, as it always was. But I can confirm that sometimes - when inactive memory makes up about 75%(!) of my 12GB - everything gets sluggish and slow, beach balls... purge helps.
It might be a problem of some applications. The other day I tried to convert some CDs to AAC 256 that I had accidentally ripped as ALAC to my HDD. I used XLD and it filled up that blue inactive memory section pretty quickly.
I wouldn't know what's causing this but it sure is annoying when it happens. If there is nothing I can do about it myself (pls let me know if there is), I hope Apple or the 3rd party developpers are working on it.
P.S. Is there a way to find out exactly which process is responsible for this quick increase in inactive memory when it happens?
Currently Being ModeratedApr 4, 2012 10:35 AM (in response to Joasousa)
I have similar problems. Late 2011 MBP with 4GB. I only use very basic apps: Chrome, MS Word, Preview. Why I should have any spinning balls or 2.75 GB of Swaps is beyond me. I am not a programmer at all, so I have no insight, but something is amiss. This is a 2 month old machine, and I recently did a complete fresh reinstall of Lion.
I just ordered an additional 8GB of RAM thinking this would solve the problem. From some comments here, I am concerned it won't.
Anyway... I did submit feedback to Apple.
Currently Being ModeratedApr 24, 2012 1:30 AM (in response to Joasousa)
There are evident problems in memory management in os x ...
please, take a look at my post: https://discussions.apple.com/thread/3899357
also, i recorded a screen video, where the system starts to hang when all the free memory is gone, and inactive memory is 4-5 GB ! http://www.youtube.com/watch?v=u5wZwZh61_4&feature=player_embedded
Currently Being ModeratedApr 24, 2012 3:28 PM (in response to egremyl)
We can only hope that Mountain Lion makes MacOS slimmer, because right now, when comparing it to Windows 8, it's a resource hog similar to Vista. I love my Mac hardware, but Lion if extremely disappointing.
Currently Being ModeratedApr 26, 2012 8:39 AM (in response to Joasousa)
Any ideas here - would be grateful for any assistance (as this cannot be normal):
Background info- boot with no open windows about 4 hours ago, used all the standard office programs, some photoshop. Thats all.
Late 2011 mac book (higher spec)
PS: this problem starting coming up recently (no issues before a week ago, bought it the second it came out with 8GB ram)
Currently Being ModeratedApr 26, 2012 8:55 AM (in response to jackflash3r)
Whatever you may read here, it is not normal for Lion not to give inactive memory free. When it is not given free it could be the application "not fitting well". Anyway:
Start Terminal (Applications/Utilities),
to the line with the $-sign at the end type "purge" (without the quotes) then hit the enter key.
Type "Exit" on the next line, hit the enter key;
QUIT Terminal (from the menu).
Read the inactive memory in Activity Monitor.
You still need to find out why the inactive memory is not freed when necessary: for that you need some of the real professors here.
Currently Being ModeratedApr 26, 2012 9:20 AM (in response to LexSchellings)
Thanks for the speedy reply!
Purge works and does free up the inactive memory - but the question then becomes why am i doing this in the first place
It doesnt ruin my day or take too long; it can even be automated with a simple script@ http://www.icoretech.org/2011/07/how-to-recover-memory-on-mac-os-x-lion-for-free /
And I hope I dont step on any toes here - but this is something I believe I should not have to do and am completely perplexed as to why lion does not realize that 24mb of RAM is detrimental to my user experience!
Best and thanks again Lex
Currently Being ModeratedMay 15, 2012 2:14 PM (in response to LexSchellings)
This is a problem that is becoming very annoying.
I love Apple products and definitely my Macbook Pro, but an expensive machine with 4gb of memory should not slow down this much, because of (insanely) growing inactive memory. I also did an upgrade to 8gb, but the same thing is happening.
Compared to my 3 year old Dell laptop with Windows 7 on it, my Macbook Pro sometimes seems incredebly slow.
My colleagues at work appear to have the same problems...
Not that good for the Apple image I think.
The purge command helps, but we should not have to do it.
Hope they will come up with a solution.