Massive Mountain Lion memory leak

You could try uninstalling iTunes by following these instructions: https://discussions.apple.com/thread/4569207?answerId=20625974022#20625974022

Then see if the unresponsiveness problem still occurs. Indeed, as has been pointed out elsewhere (and possibly here), a low amount of free RAM isn't a problem in Mac OS X as long as the machine is responsive, due to the system's use of inactive RAM when required. If the unresponsiveness still occurs, then it's not iTunes causing the problem. If it doesn't occur, you can try download a fresh install of iTunes from here: http://www.apple.com/uk/itunes/download/

Did you also try running iTunes while in Safe Mode? What happens?

If it still doesn't work after reinstalling I'm not sure I can help.

By the way, re your comment about Apple, this thread might help point you in the right direction.

https://discussions.apple.com/thread/3551533?start=0&tstart=0

From the data that I supplied that it can be seen that the OS keeps grabbing available RAM and then it does not use inactive RAM but rather uses the hard disc for virtual memory. This suggests an OS problem since an efficient operating system would swap out 'inactive' memory to the disc and replace this with the memory required by the current working resource.

The common factor in all of my memory leaks has been that iTunes has been started, podcasts downloaded and then iTunes closed. It would appear that as part of the iTunes closedown that a degree of iTunes database maintenance is completed and this could be the potential problem. But to confirm that an iTunes developer would need to comment.

In the past I have found that the OS has managed to grab nearly all of the disc space, the problem only surfacing when you try to swap to another application and response times are infinite. The only option then is a 'hard' rather than 'soft' reboot since closedown would prabably take a week or so. This also often leads to loss of data within open applications.

I don't know why many people keep saying that "inactive memory" is just normal. I also notice terrible slowdown after running some routine applications, such as chrome, keynote, etc, especially after some "sleep". I am sure that it's not a hardware problem, as after a reboot, everything runs so smoothly. Mountain lion should be carefully examined to identify some careless memory management design.

I quite agree with your comments. There is a lack of understanding as to how memory is used within a computer and its operating system. As for virtual memory, well it is not enderstood at all. From my viewpoint the alarming speed with which the OS uses disc space for memory is very worrying indeed for applcation and battery performance.

Hibernation does seem to be a major problem deepnding on the applications being exected when hibernation starts.

This is a design problem within the OS that will, I hope, be addressed within the latest release of Mavericks. As an aside, from the pre-releae hype for Mavericks, Apple are addressing a number of known (well to them) memory problems.

So for me it is teach myself Cocoa, XCode, remember some UNIX and start to delve into the OS. Perhaps I should enlist the help of the Devil's Advocate?

dalibocai wrote:

I don't know why many people keep saying that "inactive memory" is just normal.

Because it is, and unused memory is no use at all.

All right. Inactive memory is not important. How do you explain the fact that so many people observe an obvious correlation between the increase of inactive memory and dramatically degraded performance? It's a design defect. Apple engineerers, please admit it and do something. We love MAC and we sincerely hope such serious problems can be solved timely.

I completely agree with dalibocai.

dalibocai wrote:

All right. Inactive memory is not important. How do you explain the fact that so many people observe an obvious correlation between the increase of inactive memory and dramatically degraded performance?

How do you explain the millions who do not?

It's a problem on your system, not OSX generally, when you accept that and start looking for the cause rather than assuming that it is a general problem that millions haven't noticed yet you may get somewhere!

sergibondarenko wrote:

I completely agree with dalibocai.

That's your opinion, good luck with locating the problem.

Your way to address technical problems is fundamentally wrong. Say you developped a software, and millions of people use it. A tiny portion of users, say 5%, reported the software freezes their computer from time to time. Do you look into your software to check whether its design has problems or you blame the 5% by saying that the other 95% didn't complain at all? By the way, I have several friends, who encountered the same problem. But they don't want to waste their time by posting it on Apple forum or somewhere else. So the seemingly 5% can be actually 20% or more.

Csound1

Csound1It is the opinion of many other people around the world.

I have masters degree in computer science. Don't try to say I installed my system improperly, I know how to use computers.

sergibondarenko wrote:

And it is the opinion of many other people around the world.

How many, supply some attribution.

dalibocai wrote:

Your way to address technical problems is fundamentally wrong.

Detail the correct method here then.

Csound1

What programs do you usually run on your mac?

If it's a web browser, mail, skype and itunes, I don't wonder you haven't notice any performance change.

But if you run something more serious like Xcode, AutoCAD and Photoshop, you will notice the performance drop very quickly.

Tell me your VM size and Page Out levels please, lets see what you are suffering from.

I have no performance issues on any of my Macs using all 3 of the programs you mention, I also run ProTools without issue, there is no problem that affects OSX generally, just poorly setup installations.

So, how about that info.