Q: Your System has Run out of Application memory

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?

The fusion drive sems to come up in association with this regularly, and I have also seen an apparant correlation with iMacs using 32GB of 3rd party Ram (except for OWC sourced Ram).

Can you remove 2 of the Ram chips and run on 16GB for a while (long enough to test at least)

But I would like to see an Etrecheck report, run it and post the result here.

EtreCheck version: 1.9.12 (48)

Report generated 16 June 2014 15:18:24 BST

Hardware Information:

          iMac (27-inch, Late 2012) (Verified)

          iMac - model: iMac13,2

          1 3.2 GHz Intel Core i5 CPU: 4 cores

          32 GB RAM

Video Information:

          NVIDIA GeForce GTX 680MX - VRAM: 2048 MB

                    iMac 2560 x 1440

System Software:

          OS X 10.9.3 (13D65) - Uptime: 0 days 0:2:27

Disk Information:

          APPLE HDD ST3000DM001 disk1 : (3 TB)

                    EFI (disk1s1) <not mounted>: 209.7 MB

                    disk1s2 (disk1s2) <not mounted>: 3 TB

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

          APPLE SSD SM128E disk0 : (121.33 GB)

                    EFI (disk0s1) <not mounted>: 209.7 MB

                    disk0s2 (disk0s2) <not mounted>: 120.99 GB

                    Boot OS X (disk0s3) <not mounted>: 134.2 MB

USB Information:

          Apple Inc. MacBook Air SuperDrive

          Apple Inc. FaceTime HD Camera (Built-in)

          Apple Inc. BRCM20702 Hub

                    Apple Inc. Bluetooth USB Host Controller

Thunderbolt Information:

          Apple Inc. thunderbolt_bus

Gatekeeper:

          Mac App Store and identified developers

Kernel Extensions:

          [not loaded] com.GenesysLogic.driver.GLLUD (8.8.8 - SDK 10.6) Support

Startup Items:

          ProTec6b: Path: /Library/StartupItems/ProTec6b

Launch Daemons:

          [loaded] com.adobe.fpsaud.plist Support

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

          [loaded] com.prosofteng.KXInstaller.plist Support

Launch Agents:

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

          [running] com.canon.MFManager.plist Support

          [running] com.epson.Epson_Low_Ink_Reminder.launcher.plist Support

          [running] com.epson.eventmanager.agent.plist Support

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

User Launch Agents:

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

          [loaded] com.citrixonline.GoToMeeting.G2MUpdate.plist Support

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

User Login Items:

          Google Notifier

          Spyder3Utility

          AdobeResourceSynchronizer

          ElementsAutoAnalyzer

          HP Scheduler

          HPEventHandler

Internet Plug-ins:

          FlashPlayer-10.6: Version: 14.0.0.125 - SDK 10.6 Support

          QuickTime Plugin: Version: 7.7.3

          Flash Player: Version: 14.0.0.125 - SDK 10.6 Support

          Default Browser: Version: 537 - SDK 10.9

          OfficeLiveBrowserPlugin: Version: 12.3.6 Support

          Silverlight: Version: 5.1.10411.0 - SDK 10.6 Support

          JavaAppletPlugin: Version: Java 7 Update 51 Check version

Safari Extensions:

          ExifExt: Version: 1.9.6

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:

          CitrixOnlineWebDeploymentPlugin: Version: 1.0.105 Support

          fbplugin_1_0_3: Version: (null) Support

3rd Party Preference Panes:

          Flash Player  Support

          Java  Support

Time Machine:

          Mobile backups: OFF

          Auto backup: YES

          Volumes being backed up:

          Destinations:

                    Data [Network] (Last used)

                    Total size: 3 

                    Total number of backups: 21

                    Oldest backup: 2014-06-07 06:54:16 +0000

                    Last backup: 2014-06-16 13:15:58 +0000

                    Size of backup disk: Excellent

                              Backup size 3  > (Disk size 0 B X 3)

          Time Machine details may not be accurate.

          All volumes being backed up may not be listed.

Top Processes by CPU:

              13%          mds

               4%          Mail

               2%          WindowServer

               1%          Safari

               1%          fontd

Top Processes by Memory:

          164 MB          Finder

          131 MB          WindowServer

          131 MB          com.apple.IconServicesAgent

          131 MB          Mail

          98 MB          mds_stores

Virtual Memory Information:

          26.33 GB          Free RAM

          3.56 GB          Active RAM

          464 MB          Inactive RAM

          1.65 GB          Wired RAM

          401 MB          Page-ins

          0 B          Page-outs

Your system looks reasonably clean. Was this system migrated or was 10.9 installed onto an erased HD wih no Migration Assistant data transfered at all?

The items below are the ones that I would either update (if they need it) or remove them in an attempt to isolate the memory issue to one peice of software.

Michael Haffey Wrote:

  

Kernel Extensions:    

           [not loaded] com.GenesysLogic.driver.GLLUD (8.8.8 - SDK 10.6) Support

 

Startup Items:

          ProTec6b: Path: /Library/StartupItems/ProTec6b

 

Launch Daemons:

          [loaded] com.adobe.fpsaud.plist Support

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

          [loaded] com.prosofteng.KXInstaller.plist Support

User Launch Agents:

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

          [loaded] com.citrixonline.GoToMeeting.G2MUpdate.plist Support

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

 

Search the names if you don't know what they are. If you don't need them, remove them.

I would also disable your login items (logout all users, log back in, hold shift as you click the login button & hold it untill the desktop becomes active). If the memory issue reappears you can assume that the login items are not part of it.

Delete the .plist for the failing Adobe job it should be in ~/Library/LaunchAgents/com.adobe.arm… (use the Finders 'Go Menu > (hold alt), select Library to open the hidden folder). Then open your Adobe apps & ensure they are all current versions.

I agree plus:

User Login Items:

          Google Notifier

          Spyder3Utility

          AdobeResourceSynchronizer

          ElementsAutoAnalyzer

          HP Scheduler

          HPEventHandler

The Google and HP stuff is not needed, as for the others I am not sure what they are and if they are needed.

And where did the Ram come from, is it Apple, or OWC?