Your System has Run out of Application memory

Did the store use Migration Assistant to bring over User data?

EtreCheck will list what is actually running.

http://www.etresoft.com/etrecheck

If it's entirely clean I would just return it to the store, they don't seem to have left it in a working state.

I'm also having the same problem. I have a Retina MacBook Pro with 16 GB of memory and a late 2013 iMac with 32 GB of memory. Both of them occasionally display the "system out of application memory" message and invite me to force quit paused applications. With that amount of physical memory plus disk swapping, this should be impossible, yet it just happened while I was using only two applications, Mail and Safari. Oh, and I've never heard of a "paused application" before, either.

I have never seen this error message before, not even in the iMac that had only 512MB of memory. Apparently this is a bug in Mavericks' memory management tricks, which makes sense because they are brand new and fancy. The developers must be very embarrassed, and their manager is probably metaphorically ready to rap their knuckles with a ruler.

I bet the fix is already in the works. I hope it makes it into 10.9.1.

I'd recommend creating a new thread with your system info. This is getting long with many different ideas on why the OS may be running out of Memory.

It's possible for system modifying 3rd party code is the reason for all your memory disappearing.

"NONE ARE THIRD PARTY"

That's what you said.

Google Chrome is, and it's a poorly written app that has caused issues for many users.

Remove it and test again.

Same problem here since I migrated to Mavericks. I have a 32GB iMac bought 8 months ago. I had thought 32GB would be enough.

"Remove it and test again".

Er, why? Does Apple pay customers to do debugging. Chrome is widely used. It may not be a great application, but if suddenly it causes problems under Mavericks, I'd like to know what Mavericks is doing wrong, not Chrome.

Hmmm, I'd like to know why Chrome haven't updated to work in a new OSX despite having access to beta versions of the OSX and........oh, it's Google. Of course. Not Apple's job to fit in with Google's inability to update their software.

Pete

The problem with your reply, Peter, is that it doesn't address two points

• Why doesn't Apple (apparently) do regression testing with common applications? I worked for several years in hardware product development and we always tested common third party attachments with new products before announcement.
• Why should customers be doing this kind of basic debugging?

Don't get me wrong. I am an Apple fan and have converted more people than I can remember to Apple, but I am disappointed in this specific case and, looking through the forums here, it appears that a good deal of other innocent Apple customers have been caught out.

You know I could simply come back and say

1. Why would Apple spend that much time helping Google with their browser mess, when they have their own Safari Browser to concentrate on?

2. 'Debugging' has been part and parcel of every OS release ever. Nobody can replicate every workflow and every combination of third party apps ad and every computer 'genius' who likes to tune up their machine. The viables are impossible to test or we would still be back at OS6 and Windows 98.

I could say all that,but I won't.

Cheers

Pete

1. Why would Apple spend that much time helping Google with their browser mess, when they have their own Safari Browser to concentrate on?

a. You're assuming this problem is caused by Chrome.

b. Because you don't want to annoy happy customers who use this common application.

2. 'Debugging' has been part and parcel of every OS release ever. Nobody can replicate every workflow and every combination of third party apps ad and every computer 'genius' who likes to tune up their machine. The viables are impossible to test or we would still be back at OS6 and Windows 98.

No you can't duplicate every workflow. But looking around these forums this seems to be quite a common problem, which apparently didn't exist with the previous release.

Michael Haffey wrote:

No you can't duplicate every workflow. But looking around these forums this seems to be quite a common problem, which apparently didn't exist with the previous release.

Looking around these forums is likened to walking into a hospital ward. You will only see sick people. Here you will only see a tiny amount or representation of the many many millions of Mavericks users worldwide. They have no reason to come here.😉

And if you care to read though the forums, even a quick perusal, you will find that this OSX is no different from any other release, probably better so, when you look at what people complained about with all previous OSXs.

Cheers

Pete

You can of course do nothing and wait in hope that it will fix itself. It's entirely your choice.

Good luck.

1. This IS a widespread problem caused by a memory leak.

2. The leak is triggered by a large number of apps, INCLUDING Apple core apps like Mail, Calendar and Aperture

3. Apple WILL TRY to fix this in the first maintenance release

4. We had a similar issue with 10.8

5. YES! The testing manager in charge with regression testing should be fired

6. NO! Customers should not be on the hook for troubleshooting MacOS or any commercial software.

Having said all that, we DO live in an imperfect world ... ;-)

Apple seeded Mac OS X 10.9.1 last week, so, we hope that it fixes this annoying issue.

Best regards,

Leonardo

I joined this discussion because I wanted to know if this problem was specific to me and if there was a fix. The anwer is that it is a bug and the fix is to wait for Apple to fix it. The problem is in the new method of managing memory, not with anything a user does. Apple will fix it as soon as they can.

No, the testing manager should not be fired. The first version of any software has bugs, sometimes conspicuous ones, either because they only become apparent after the software is released, or because the software was deliberatly released with the bug, if it is cosmetic, does not harm anything, or is just an inconvenience.

I found out what I needed to know, and I'll wait.