-
All replies
-
Helpful answers
-
Nov 23, 2013 8:26 AM in response to Paul J Dunningby Rich1955,Recent update made no difference to my memory leak problems. See other thread.
-
Nov 24, 2013 12:47 AM in response to Paul J Dunningby Najinsky,★HelpfulI had the same issue, specifically with brushed adjustment. I actually ran out of SSD space due it (lost 30GB in 2 hours of brushed adjustments). I reported it to Apple and they contacted me to get more info on the issue.
After sending a small library and my system settings to them, they came back and suggested it my be related to having an on-screen proofing profile set and wanted me to try and make the problem again after turning that off.
I've only been able to test for short periods of time for the moment, but on the surface, the problem seems to go away when on screen proofing is turned off. I report this back to them and said I would report back when I have more time to test it more throroughly
I saw there was an Application update a few days ago, but I didn't see this issue mentioned specifically as a fix.
Edit: I forgot to say, the storage space returns after quitting Aperture. I suspect it's keeping all the old temporary versions of the TIFF files that get made from the brushed adjustment.
-Andy
-
Nov 24, 2013 2:31 AM in response to Najinskyby Rich1955,Andy,
thanks for your response. Seems to be the same problem I have. Mainly brushed adjustments but also edge sharpening which makes a signifcant size tiff mask too. I have never had on screen proofing profile turned on so not cause for me. Looking back at 2010 (?Lion) , Aperture had a memory leak then which was denied by Apple I believe and some wise sage said wait, Apple will quietly fix it and it will go away. Well I'm hoping the same, but not likely unless they get enough reports. Thanks for reporting your problem. Those without Applecare don't seem to have a reporting input to Apple.
Like yours the memory completely restores on restarting Apple and the problem goes away for half dozen images or so. Luckily with an SSD restart is quick but annoying. Clearly Aperture Mavericks problem as Lion and mountain Lio were fine. Hope they fix it soon.
Regards,
Rich
-
Nov 24, 2013 11:41 AM in response to Paul J Dunningby Steven Slupsky,I have had three kernel panics today as a result of brushing in adjustments. Running 3.5.1 and Mavericks.
-
Nov 24, 2013 11:47 PM in response to Paul J Dunningby JonThor59,I'm also having the same issues. I have 24GB in my 2010 Mac Pro which quickly gets eaten up with only a few adjustments in Aperture. I'm getting tired of quitting Aperture to clear it out.
-
Nov 26, 2013 3:14 AM in response to Steven Slupskyby Rich1955,Steven, thanks. Any ideas how to let Apple know if not in Applecare? or do they read these forums?
-
Nov 26, 2013 3:16 AM in response to JonThor59by Rich1955,Wow.! with 24GB should be fast and smooth. Musy be aleak. have you been able to let Apple know yet?
-
Nov 26, 2013 4:55 AM in response to Najinskyby Paul J Dunning,Hmm - turning off on screen proofing seems to fixed it for me (or at the very least made the problem go away). With six images brushing in curves, the memory pressure did not grow like it did - it remained steady. So I think I’ll go with that option off for the time being and see how I get on.
-
Nov 26, 2013 8:05 AM in response to Paul J Dunningby Rich1955,Paul, that's good for you. No good for me as on screen proofing profiles are switched off.
Would like Apple to fix Aperture.
Aperture on a MBPro was amazing but is now a PIA.
-
Nov 26, 2013 8:45 AM in response to Rich1955by léonie,Steven, thanks. Any ideas how to let Apple know if not in Applecare? or do they read these forums?
Sometimes the developers will be looking here, but the safest way to let them know of any problems is the feedback form built into Aperture's application menu: Aperture > Provide Aperture feedback.
-
Nov 26, 2013 9:19 AM in response to léonieby Rich1955,Leonie,
thanks. Don't know how I missed that. I have sent a report off today.
Regard,
Rich
-
Nov 29, 2013 6:19 PM in response to Paul J Dunningby sorinfromtoronto,I can confirm that turning proofing off seems to at least alleviate the problem. I am pretty sure onscreen proofing is not the root cause, but it is one of the features that seems to trigger the memory leak in 10.9.
As I suggested before, everyone needs to use whatever workaround works best for their manifestation of the problem. Do not waste too much time, since Apple is most certainly aware of the problem and will again (silently) fix it as they have done before.
-
Nov 29, 2013 7:58 PM in response to Rich1955by Steven Slupsky,Sorry I missed your message. The official line in the past was Apple did not visit these forums. However, it appears to me that has changed recently and I've seen posts from people that look like they are from Apple.
Still a good idea to send feedback though. I did as well!
I have not had a chance to try turning off proofing yet. Will try to do so over the weekend.
Regards,
Steve
-
Nov 30, 2013 2:13 AM in response to léonieby Paul J Dunning,Seta report as well, with steps to reproduce the problem.
-
Nov 30, 2013 2:19 AM in response to Paul J Dunningby léonie,Sure, if you have a Developer account, https://developer.apple.com/programs/ ,
it would be best to use the bug-reporter form. Only the majority of our Aperture users here will not be developers and not have access to the bug-reporter.
