Currently Being ModeratedDec 6, 2013 11:25 AM (in response to george152)
Do you have On Screen Proofing enabled? Then try if disabling it will solve the memory leak issue, see Frank Caggiano's post: Re: Aperture 3.5 repeatedly crashes as 'memory full' despite 32GB RAM https://discussions.apple.com/message/24000578?ac_cid=tw123456#24000578
Currently Being ModeratedDec 10, 2013 10:38 AM (in response to george152)
The on screen proofing did not as I said seem to resolve the issue. After several more restarts of my computer and aperture, I ran some photo adjustments and watched as the memory usage went up. Not as rapidly as before, but after ten minutes it was beyond the original 8gb of my unit. After 30 minutes it was using 12gb and when checking usage on the activity monitor there was something in the red. ( QTKitServer with a number and aperture not responding after it) I opened this up and it listed a number of hangs and numerous other items, all beyond my level of understanding. Aperture recovers more rapidly now with the 32gb of memory, and after I quit the app and then reopen then recheck the activity monitor the server item in the red is no longer there. Yet it reappears after only 15 min. of editing. Just adding this as an update to my situation. I have been able to edit raw files now for two hours before getting down to 8gb of memory left on my system.
Currently Being ModeratedDec 10, 2013 10:50 AM (in response to george152)
Yet it reappears after only 15 min. of editing.
Do you see any error messages or diagnostic messages in the Console window, when the memory goes down? You can launch the Console.app from Applications > Utilities.
Are there any new messages, that might be related to Aperture, in the Console window, when you are editing?
Currently Being ModeratedDec 10, 2013 11:50 AM (in response to george152)
As suggested I run another test, it took 20 minutes for the same event this time. Have no idea as to its signifcance, I use computer as a tool, I am no expert on all its workings. Console did come up with this at the time of event. Not at all familiar with code and such, thats why one asks for help. Thanks.file:///Users/gnkx2/Desktop/Screen%20Shot%202013-12-10%20at%2011.37.40%20AM.png
Currently Being ModeratedDec 10, 2013 12:03 PM (in response to george152)
The screenshot did not upload. But it would be easier to read anyway, if you just copied a short selection of the error messages and pasted the text directly into your post.
To post a screenshot, click the "Camera" icon in the toolbar of the editor, and the use the file chooser to upload the image. If you just drag a file into the window, the link will be broken, unless it is an uimage already on the forum servers from a previous post.
Currently Being ModeratedDec 10, 2013 12:34 PM (in response to george152)
No problem BTW, what is your Aperture version?
It might be a problem with a plug-in or external editor, but also due to incompatible kernel extensions. Have you installed any software at all, that might not be compatible with Mavericks?
In a few cases the error messages you are seeing were related to an Aperture Library that needed repairing, but in your case you are already testing with anew library. Or has Aperture crashed in the meantime, so that repairing would again be necessary?
Currently Being ModeratedDec 10, 2013 1:13 PM (in response to george152)
Well it is the current version 3.5.1 I have auto updates on. Also I have not added any plug ins.
Have not had a crash recently. As far as I know non of the software that I have installed is incompatible with my system, I purchase directly from the app store, and have only installed some Adobe after this all began.
As this issue began after I installed Mavericks. I had several crashes and this was after having the same issue on my Macbook pro, also with Mavericks. At the time I decided that my 2008 17' was showing it's age so I went with a
new 27" I-Mac Which I started using this past August, with a fresh install of Aperture and import of new photos into the pictures folder as a referrenced library from that point. No problems at all untill after installing Mavericks back in October and issues began. Alas I have no such issues on my 2008 I-Mac running aperture. Of course this is without Mavericks and running Mountain Lion. The repairing of libraries after crashing is anoying, I have trying to avoid crashing, so far successful.
Currently Being ModeratedDec 10, 2013 1:48 PM (in response to george152)
have only installed some Adobe after this all began.
The Adobe NIK collection? There are several threads reporting problems with this suit on Mavericks. The Link from the Adobe Site to the newer Google download specifies the requirements as "Mac® OS X 10.6.8 through 10.8" - Mavericks is excluded.
Currently Being ModeratedDec 11, 2013 9:32 AM (in response to george152)
Currently Being ModeratedDec 15, 2013 10:59 AM (in response to george152)
Another update on my status, memory usage is still up and I just keep a watch on the activity monitor for things going into the red. Then I restart and get back to work. Unfortunate but patiently waiting for something to change. Important note to some; found out today that Canon updated some of their utility software for certain cameras.
On 12/12/2013 specifically for osx, unsure of it's significance. In relation to this situation. But thought it was worthy of mention.