Your System has Run out of Application memory

the new report is:

EtreCheck version: 1.9.11 (43) - report generated June 11, 2014 at 10:38:07 AM GMT-5

Hardware Information:

MacBook Pro (Retina, Mid 2012)

MacBook Pro - model: MacBookPro10,1

1 2.3 GHz Intel Core i7 CPU: 4 cores

8 GB RAM

Video Information:

Intel HD Graphics 4000 - VRAM: (null)

NVIDIA GeForce GT 650M - VRAM: 1024 MB

System Software:

OS X 10.9.3 (13D65) - Uptime: 0 days 1:57:20

Disk Information:

APPLE SSD SM256E disk0 : (251 GB)

EFI (disk0s1) <not mounted>: 209.7 MB

Macintosh HD (disk0s2) / [Startup]: 250.14 GB (34.44 GB free)

Recovery HD (disk0s3) <not mounted>: 650 MB

USB Information:

Apple Inc. FaceTime HD Camera (Built-in)

Apple Inc. Apple Internal Keyboard / Trackpad

Apple Inc. BRCM20702 Hub

Apple Inc. Bluetooth USB Host Controller

Thunderbolt Information:

Apple Inc. thunderbolt_bus

Gatekeeper:

Anywhere

Kernel Extensions:

[not loaded] com.microsoft.VirtualPC.Networking (7.0.1) Support

[not loaded] com.microsoft.VirtualPC.OSServices (7.0.1) Support

Startup Items:

PenTabletDriver: Path: /Library/StartupItems/PenTabletDriver

Problem System Launch Daemons:

[failed] com.apple.AOSNotificationOSX.plist

[failed] com.apple.softwareupdated.plist

[failed] com.apple.wdhelper.plist

Launch Daemons:

[loaded] com.adobe.fpsaud.plist Support

[loaded] com.adobe.SwitchBoard.plist Support

[loaded] com.microsoft.office.licensing.helper.plist Support

[loaded] com.oracle.java.Helper-Tool.plist Support

[not loaded] com.teamviewer.teamviewer_service.plist Support

Launch Agents:

[not loaded] com.adobe.AAM.Updater-1.0.plist Support

[loaded] com.oracle.java.Java-Updater.plist Support

[not loaded] com.teamviewer.teamviewer.plist Support

[not loaded] com.teamviewer.teamviewer_desktop.plist Support

User Launch Agents:

[loaded] com.adobe.ARM.[...].plist Support

[loaded] com.google.keystone.agent.plist Support

User Login Items:

iTunesHelper

VMware Fusion Start Menu

Dropbox

USBOverdriveHelper

PenTabletDriver

Google Drive

Internet Plug-ins:

FlashPlayer-10.6: Version: 13.0.0.214 - SDK 10.6 Support

QuickTime Plugin: Version: 7.7.3

AdobePDFViewerNPAPI: Version: 11.0.06 - SDK 10.6 Support

AdobePDFViewer: Version: 11.0.06 - SDK 10.6 Support

Flash Player: Version: 13.0.0.214 - SDK 10.6 Outdated! Update

Default Browser: Version: 537 - SDK 10.9

SharePointBrowserPlugin: Version: 14.0.0 Support

Silverlight: Version: 5.1.20913.0 - SDK 10.6 Support

JavaAppletPlugin: Version: Java 7 Update 51 Check version

Safari Extensions:

Dashlane: Version: 2.4.0.56001

Audio Plug-ins:

BluetoothAudioPlugIn: Version: 1.0 - SDK 10.9

AirPlay: Version: 2.0 - SDK 10.9

AppleAVBAudio: Version: 203.2 - SDK 10.9

iSightAudio: Version: 7.7.3 - SDK 10.9

iTunes Plug-ins:

Quartz Composer Visualizer: Version: 1.4 - SDK 10.9

User Internet Plug-ins:

Dashlane: Version: Dashlane 1.0.0 - SDK 10.7 Support

3rd Party Preference Panes:

Flash Player Support

Java Support

Time Machine:

Time Machine not configured!

Top Processes by CPU:

21% filezilla

4% WindowServer

1% fontd

0% Google Drive

0% Google Chrome

Top Processes by Memory:

639 MB firefox

172 MB Finder

131 MB mds_stores

123 MB com.apple.IconServicesAgent

106 MB com.apple.quicklook.satellite

Virtual Memory Information:

3.25 GB Free RAM

2.45 GB Active RAM

1.02 GB Inactive RAM

1.01 GB Wired RAM

1.69 GB Page-ins

32 MB Page-outs

I don't understand why you have so many failed services but if you're happy I'm happy.

🙂

🙂

Mavericks uses a different memory management than previous versions of OS X. Using Memory Clean conflicts with current memory management. I suggest you remove.

Yes it in the preference of memory clean and as the memory bleeds to low and not out it restores lost memory a bandade until Mavericks gets fixed. It's only bad advice if it dosen't work I have been up for weeks since I installed memory clean I am running Mac because I can't spend hours trouble shooting with no results, that's why we have Mac's but that seems to be changing with no updates to fix 10.9.3 still does not fix.

darryl-1 wrote:

Yes it in the preference of memory clean and as the memory bleeds to low and not out it restores lost memory a bandade until Mavericks gets fixed.

Mavericks is not broken,

Memory Clean is junk, stop promoting it here.

I am really sorry. I love Apple, my iMac and OSX.

However, wrt application out of memory errors, Mavericks is broken. I've had this error several times when all that has been running is Aperture and Safari. And all I've been doing in Aperture is Enhance, sharpen and skin smoothing.

Apple really needs to fix this.

So the millions of users who are not having your problem. how do you explain them?

If you continue to use a product like Memory Clean that goes against how Mavericks manages memory, you are going to have issues.

Csound1 wrote:

So the millions of users who are not having your problem. how do you explain them?

That's really not difficult. They are using different applications that do different things in Mavericks.

It's pretty clear that Aperture, an Apple app, can cause these issues. There are other Apple apps that do so also. On your recommendation I stopped using Chrome and only use Safari now.

However, the crucial point is this: there has been a surge in these problems since Mavericks came out. When I am editing photos this can happen 2-3 times a day. Even if it were bad coding in the application, Mavericks should gracefully fail the program. It's a great pity because this is a blot on a lovely system.

Michael Haffey wrote:

Csound1 wrote:

So the millions of users who are not having your problem. how do you explain them?

That's really not difficult. They are using different applications that do different things in Mavericks.

That's a guess. (and a copout, what you said was 'I don't know')

It's pretty clear that Aperture, an Apple app, can cause these issues. There are other Apple apps that do so also. On your recommendation I stopped using Chrome and only use Safari now.

Over 300,000 Aperture users (inc me) are not having issues, again, how come you are and they are not (not another copout please)

However, the crucial point is this: there has been a surge in these problems since Mavericks came out. When I am editing photos this can happen 2-3 times a day. Even if it were bad coding in the application, Mavericks should gracefully fail the program. It's a great pity because this is a blot on a lovely system.

Unless you actually have something other than an opinion to back that up I disagree with your assessment.

I notice that there seems to be a common thread that it's down to Aperture, and other software, but on ALL of our Mavericks systems at work, we don't have any of the software that is mentioned above, we use just two applications, Maya and Photoshop.

On all of the systems that we used to run under Mavericks we had this issue, which eventually got so bad that our MD made a rather heated call to Apple in the UK and within 3 hours we had a crew of techie bods appear to look at the systems?

They spent 4 hours going through the systems, with the odd comment coming back that this is a well-known issue, and there is not a lot that we can do, in the end they put all the systems back onto Mountain Lion, as this was the only fix that they could do that would work, and stay reliable, downtime for us is a major issue as we cannot afford to let any of our clients down, and prior to this we would have to reboot about 3-4 times a day to hope that we could get a few more hours from the systems.

We were told that the issue is not the software that is running on the systems, but the OS itself, Apple know about it, but they are hoping that the new OS will sort this issue out, apparently they were told it is not a fix that a software release/update/service pack could fix, we have also since this returned a large number of the new Mac Pro's to Apple for a refund, the hardware is not the issue and they were really sweet to use, but even though we all love using Apples here, at least Windows 7 does not have the same issues, and we need reliability, something that you don’t get from Windows normally, but at least rebooting once a week is better that 3-4 times a day...

Csound1 wrote:

Michael Haffey wrote:

Csound1 wrote:

So the millions of users who are not having your problem. how do you explain them?

That's really not difficult. They are using different applications that do different things in Mavericks.

That's a guess. (and a copout, what you said was 'I don't know')

No, I didn't say "I don't know". I do know they are using different applications unless you are telling me that everyone on Mavericks uses just Safari and Aperture. I know that they are doing different things in Aperture as they are not processing my Nikon NEF (raw) images.

But let's be clear: you don't know. And you are guessing. You are clearly very talented given the number of people you've helped but you don't know what's causing this problem.

It's pretty clear that Aperture, an Apple app, can cause these issues. There are other Apple apps that do so also. On your recommendation I stopped using Chrome and only use Safari now.

Over 300,000 Aperture users (inc me) are not having issues, again, how come you are and they are not (not another copout please)

They may be using dufferent Aperture functions. They are certainly processing different photographs. And, actually, you don't know how many of these "over 300,000" are not having issues. Many might be but aren't reporting it, a common behaviour of end-users. In addition, how do you explain those Aperture users on here who are experiencing problems?

However, the crucial point is this: there has been a surge in these problems since Mavericks came out. When I am editing photos this can happen 2-3 times a day. Even if it were bad coding in the application, Mavericks should gracefully fail the program. It's a great pity because this is a blot on a lovely system.

Unless you actually have something other than an opinion to back that up I disagree with your assessment.

You disagree this is a lovely system? Hmm.

This thread - 20 or so pages and growing - is evidence, rather than opinion.

I disagree with your assessment.

There are less than 200 individual posters here, even if they all have the same problem it's a tiny fraction of the user base, well below 0.001%. So let's look at it in a more useful fashion. What exactly is the link between this small fraction of installations that is causing this issue?

Proper information about what exactly is running behind the scenes would be invaluable, and yet so rarely forthcoming.

If you think that this is a system wide bug (and I don't) then your hands are tied by that.

As I write this, you have 34,270 points. That shows you know a good deal and have been very helpful.

Now what I have is an iMac with 32GB memory and a Fusion disk with Mavericks 10.9.3. Just using Aperture wit Safari running in the background I can see the system generate the out of Application memory error 2-3 times a day when I am doing a lot of simple editing. It can even give this to me as soon as I try to Resume after the system was put to Sleep.

So, if it's not a system bug, what is it? What might it be likely to be?