I'm having a problem with Safari Web Content.
I've jst re-loaded Mountain Lion in a brute forcve attempt to resolve my issue, but it's still occurring.
The issue is: with very little running, if I run Safari and bounce around a few websites, I can easily consume all my memory. I end up with this:
As you see, Active memory is too high (before this test I had Mail open, and Avtive memory was about 2GBm what you might expect normally).
Actibve memory had actually peaked at about 3/4 of the total, but then some must have got swapped out to Inactive.....giving us the picture above.
But look at the Real Mem occupied by Safai Web Content! That can't be right, surely.
Nevertheless, I'm led to believe that OSX's memory management algorithm's will swap out Inactive for Free when it is required....well, this isn't happening. I saw Free memory down to 7MB at one point, not a typo. Everything grinds to a halt.
If I am patient, and try to Quit Safari, I end up back here:
Clearly showing that if I manage to kill Safari, the memory gets freed up again.
I understand why OSX wants to handle memory with the Inactive concept - "you've just closed Word, but maybe you'll open it again in the next ten minutes so we'll leave it in memory, inactive, so when you try and open it, it will open really quickly". Right now, I'd rather turn that freature off and have memory behave more primitively and take the hit on re-opening.
As I mentioned, I reloaded OSX Mountain Lion and the problem persists. When you re-load or upgrade your OS, there are many configuration settings (desktop, mail, safari) that are kept so that the upgrade looks seamless; clearly whatever is corrupting me here has been kept also. For that reason I'm loathe to go to Mavericks, because I presume the same corruption would exist (and also I hear Mavericks is still a bit shaky with the native Mail app).
What config type files should I look to safely delete and have the OS rebuild? Any ideas?