Currently Being ModeratedJan 27, 2013 12:14 PM (in response to ds store)
I do not see anything specific in there related to the Terminal app and resinstalling OSX, followed by all of the other setup is not an option.
As a matter of fact, I just checked my Macbook Air (late 2012 model) and it has exactly the same issue with Mountain Lion 10.8.2, so this is in fact an OSX issue that needs engineering support to locate and fix, not simply "trial and error" drastic time consuming changes, I don't have time for that.
Currently Being ModeratedJan 27, 2013 12:38 PM (in response to TheForce61)
Now I just got a popup saying my startup disk is full, even though disk utility shows 124Gig still free, and terminals are frozen indefinately, and I am in the middle of runnign a critical job that will cost me two days work if it does not complete!
This is a stock RMBP with 256G flash, and I have not made any partition changes or anything. Seems the freezing terminals may have something to do with virtual memory cache (leak) or something, but like I said, it even happens on Macbook Aor, and I wasn't even runnign job on there.
I just killed Activity Monitior, and terminals unfroze, perhaps a leak or full cache for Activity Monitor?
And, yet another popup saying "Your Mac OS X startup disk has no more space available for application memory", is this a virtual memory issue?
How do I tell it to use X amount and not try and use more?
Clearlyu Mountain Lion 10.8.2 has virtual memory issues
Currently Being ModeratedJan 27, 2013 1:16 PM (in response to TheForce61)
OK, looks like a terminal memory leak, virtual memory for terminal is 56G, and now I am hosed, going to lose a couple of weeks on my startup, will have to build a linux box.
My running job shows normal swap, terminal itself shows the 56G swap and growing.
Note the only job I have running now is also running on a very old SUSE box and has been for 3 weeks, and swap on that machine is a constant 1.9G for my job. It has been runnign for one day on my RMBP, but again, the issue is terminal, not my running job.
I at least needed this job to complete, and it is hung.
I was going to use my RMBP to run these jobs until I buy a Mac Mini to do this, but I can't possibly buy a Mini if these problems are Mountain Lion related, and given the same issues are on my new Air, I have no reason to believe anything else.
Currently Being ModeratedJan 27, 2013 1:44 PM (in response to ds store)
I just spent nearly $4K on Mac computers for my startup, I do not have time and money to go buy other hardware. I am finding many people have similar issues, but have not found a solution yet,so I guess I will have to get on the phone.
This is for my business.
Currently Being ModeratedJan 27, 2013 2:02 PM (in response to TheForce61)
I do not have time and money to go buy other hardware.
This is for my business.
Currently Being ModeratedJan 27, 2013 2:09 PM (in response to ds store)
I could see maybe running linux in a virtual machine on my Mac, but only as a test to prove the terminal memory leak. Forget Windows, has no unix like environmnet.
However, It is not feasable for me to run linux in a virtual machine as a permanent solution, since what I am doing requires speed, and no other resources being comnsumed, and that doesn't fit that scenario.
The solution is going to have to be an Apple engineer helping find out why terminal has a leak and fixing it in Mountain Lion.
I am watching terminal virtual memory grow as I write, of course after having to reboot the machine and losing two days work....
Currently Being ModeratedJan 27, 2013 3:13 PM (in response to ds store)
I just confiormed it through a series of tests.
I ran some intensive perl, which the perl process itself does not increase virtual memory at all.
However, it just keeps increasing the "terminal" virtual memory indefinately, even after the perl script stops.
This proves there are some "very serious memory management issues" in Mountain LIon, related to terminal, and who knows what else.
They are only resolved by rebooting the machine, and that is only temporary.
Currently Being ModeratedJan 27, 2013 11:46 PM (in response to ds store)
I found two ways around this issue.
1. Launch the script in the background and kill terminal and close the terminal app.
2. Change the termial window "scrollback" to "10,000" from "All avialable memory".
However, if one selects "All available memory", it should not run it up until the machine freezes, so I still think this is a bug. At least I was able to resolve it.
Thanks for responding.
Btw, more isn't always better