Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • 3
    I'm with you, Ernie... in Mac OS 10.6 and 10.7 on a MacBook Pro and Mac Pro, inactive memory will creep up, and the OS will start swapping (according to "Page Ins" and "Page Outs") and the system will crawl to a stop. The inactive memory seems to never get reclaimed. I have to use "purge" to reclaim the inactive memory, and get my system active again. Commented Jul 31, 2013 at 22:08
  • 2
    Where does this popup window come from? What is the memory situation as reported by vm_stat when it does happen? What makes you so sure that there can be "too much" inactive memory "to run anything"? As far as I'm concerned, this is all hearsay that has no backing in the code that you know, actually runs in the kernel. Commented Oct 23, 2013 at 17:52
  • 2
    Does your memory allocation look anything like what Gus has presented? Here we're talking about a gigabyte wired and a gigabyte and a half active. The inactive / free ration looks fine to me in this situation. Perhaps you would ask a second question detailing the situation you have where things are breaking down? Commented Oct 24, 2013 at 18:27
  • @Eric did you ever figure out how to purge to get your inactive memory back? Commented May 20, 2020 at 4:33
  • @Ernie short answer: No. Longer answer: It's been almost 7 years from the original question, and even I (who wait years to upgrade to a new MacOS version) am up to 10.13 and 10.14, neither of which report Inactive memory anymore. I can't recall if I ever resolved the issue back on 10.6 or 10.7. I haven't noticed any similar behavior in 10.13 or 10.14. Commented May 20, 2020 at 18:56