Q: Solution for Aperture 3.5 and OSX 10.9 Maverick's crashing

I've done the recent large Mavericks upgrade and Aperture seems better behaved. Anybody else noticing that?

Yes, for me the OS X 10.9.2 update improved the memory management a lot for me, both on the MBPs and iMac.

Yes, I to have noticed the increase in the performance of 10.9.2

On my Mac the RAM usage with Aperture has gone down

Allan

Hi,

I'm using Aperture 3.5.1 on the latest version of OS X Mavericks. I have installed the latest versions and updates of both software products. The software is running on my MacBook Pro 17", i7 2.66 MHz, 8GB RAM and 2 x 240GB Intel 520 SSD's. The main SSD (hosting OS X, applications and my complete user profile) is located in the HDD bay. The second SSD is located in the DVD bay and is dedicated to my Aperture libraries only.

Aperture is hangs on a regular basis but since I moved the iCloud connection to the iPhoto (also the latest version) library, this problem has not occured anymore. I have noticed that the iCloudHelper process was using a lot of CPU time a.k.a. hanging of that process.

The crashing of Aperture and also OS X remains. OS X crashes occur rarely but always when I'm using Aperture.

Aperture crashes very often and at different actions. Still, I'm not able to reproduce this behaviour. I did notice that a lot of the crashes occur during or after applying a large number of repair/clone spots, about 200 till 300. At the moment, after applying that much repair/clone spots, I close and restart Aperture. I also noticed out-of-memory errors during this process. I always close all other applications so that Aperture can use all available memory.

When Aperture crashed and the option is showed to send the crash report to Apple, I always send it. Never got any response from Apple, though...

When Aperture has been crashed, I always repair my library before continue working on my images.

My main concern is the stability and consistency of my library.

My backup schemas are:

1 - Time Machine on a Time Capsule 2TB

2 - Aperture Vaults on my Synology NAS, 2 x 2TB WD RED's in miror configuration

3 - Time Machine backup on a secondary G-Technology G-Drive HDD 500GB

I still have all my crash reports in my Console application. I do hope that Apple will solve this problem with Aperture. I really love this application but if it remains unstable, which does not garuantee the stability and consistancy of my library, I will reconsider other applications.

With kind regards, Dennis

Thanx. I'm going to try this tonight. I will let you know the resutls.

Chiming in here. Got a brand new rMBP 15'' and Aperture causes kernal panics twice per hour on average.

I have tried re-installing Aperture, RAM test, hardware test, deleting plist, new libraries, re-installing Mavericks etc. all without success. Spent three days for diagnose.

I narrowed it down to the Geforce graphics card. It's not broken according to the hardware test, but it doesn't work well with Aperture. When I turn it off and only run on the integrated Intel Iris Pro, everything works fine. It seems to even work a little quicker. Since the power of the Geforce is the reason that I bought a new Mac (and it won't run an extenal display without the Geforce), I will send it back. Sad but true.

I hope this doesn't apply to all models but only some "lemons". I'll order another one and hope it will work then.

Just a heads up... I have been having this issue since buying a brand new rMBP last fall. I sent it back and got a new replacement I didn't see the problem for a little while then started seeing it again. It definitely seems to related to the graphics adapter but I think it is likely software since it only happens with aperture. The panic is always from accelerator code and never happen when I turn off the accelerator. Very disappointing!

Same here. The crash logs always showed the HW accelerator the most recent.

Some light editing doesn't trigger a panic but only advanced editing with several bricks and brushes.

How do you turn off the accelerator?