Previous 1 2 3 4 Next 46 Replies Latest reply: May 20, 2014 5:01 AM by daniel.montecillo Go to original post
  • tn10 Level 1 Level 1 (0 points)

    I have sent to Apple via Aperture. Let's hope they resolve this very soon!

  • Reistad Level 1 Level 1 (0 points)

    I feel a bit unsecure whether or not to upgrade to Mavericks as long as there are reports about memory problems with Aperture on older machines in version 3.5.1 I currently run Aperture 3.4.5 on my MacBook Pro mid 2009 with 8 GB RAM with OS 10.7.5.


    From the discussion I have understood that I have to upgrade to Aperture 3.5 when I upgrade to Mavericks.


    Is it safe to upgrade, or is it better to wait.

  • tn10 Level 1 Level 1 (0 points)

    I would suggest waiting to see if there is an update that addresses the problems we all are experiencing. If your current verison and OS are working well for you wait a bit and see if Apple can respond to all of the disappointment with Aperture 3.5.1 on OS 10.9.1.


    I truly like Aperture but very disappointed with the updated version in the current OS.

  • ChrissBelgium Level 1 Level 1 (0 points)

    Waiting an update, I would suggest FreeMemory, a freeware in Appstore !

  • Rich1955 Level 1 Level 1 (0 points)

    Thanks, the problem with freeing memory apps is that mine (memory clean) takes longer to free memory than closing and opening Aperture and although it clears memory once the Aperture problem arises it doesn't clear that until Aperture is restarted.



  • Vampyro Level 1 Level 1 (0 points)

    I have found one of the reasons behind the problem aperture eats memory. I have a Mac Pro with SSD hard drive and 32gb ram. I have photoshop, aperture and safari open and then I have about 7,5 gb left. But much of the used one is inactive.


    When I work in Aperture I often open files in photoshop and edit them there for special edits. They are saved as .tiffs and ofcourse automaticly viewable in aperture library. Filesize about 1gb. In aperture 3,4 there was generated previews of these files. So if I clicked on a file it would respond automaticly. But In 3.5, when you click on a file it acsessen the original. So clicking on three photoshop files draws alot of memory. I checked last night. Each time I clicked on a .tff file I lost 1gb of ram. And as soon as I had clicked 7 files memory usage was full with only 14mb left. Then it took some time to free up memory and I could continue to select more files.



    But everything works realy slowly. Aperture 3.4 was fast and responsive. 3.5 is slow. And the only thing that for me slows maverics down. Finder is a bit slow to. It seems filehandeling in aperture have changed dramaticly and now is ******. Im thinking of changing to capture one. I cant work like this. It takes to much time to wait for the computer.

  • Rich1955 Level 1 Level 1 (0 points)

    Thanks Vampyro,

    I find the same. If PSE is open the memory problem occurrs more quickly and that's with using psd files instead of Tiffs.  I leave PSE off now until needed and that also is a PITA.

    Do hope Apple fix this soon.



  • Vampyro Level 1 Level 1 (0 points)

    Acsessing tiff files with aperture have become so slow. If I click a tiff thumbnail in aperture I usualy have to wait 15seconds before it starts responding again and I can select the next one.

  • Acetone. Level 1 Level 1 (55 points)

    Since going to Mavericks and Aperture 3.5, I keep getting the alert that I've run out of memory.


    I never had this issue at all before, and was wondering does 3.5 use a lot more memory, sad/glad it's a common issue and not a fault on my system.

  • INSid Level 1 Level 1 (0 points)

    Same problems here. 2011 MBP 13". When working with large files, graphical glitches begin appearing while the image is actual sized. You can see the brush masks as solid colored lines, and other distortions are apparent. The only real fix is to restart Aperture. The trigger is often just adding another Adjustment or brush stroke.


    I don't see the program slowing down as much as I did before Mavericks thanks to memory compression. But these errors are aggravating to say the least.

  • increatyv Level 1 Level 1 (0 points)

    MacbookAir mid 2011.

    Same problem: since Maverick update, Aperture 3.5 does'nt work correctly: same black screen or strange display problems, certainly link to memory issues. I need to restart Aperture, several times, to be able to work.

    Please, Apple, fix this very very frustrating Aperture memory leaks...

  • Rich1955 Level 1 Level 1 (0 points)

    Weird solution to problem.

    Some people have had significant display problems with Aperture only since Mavericks was launched. This occurs when working with large raw files and usually when memory drops below a certain level.

    Apple have said that this may be due to On screen profiling and have advised that that should be turned off. This has helped some and made no difference to others. It occurs more quickly if photoshop elements is running but also occurs when it is not. Withe PSE running I can only process a handful of file before display problems (black screens, visible masks, stuck zoomed previews) occur. Turning Aperture off and restarting it restores the correct previews and shows no lost work.

    Apple support asked me to make notes of the problem, crate a diagnostic file when it occurs and to record a screen display of my using Aperture until the problem occurs.

    Here's the odd thing and maybe some of the forum experts can explain this, when running Quicktime FULL screen recording and using Aperture, the problem disappears!! Completely. Whether PSE is on or not, Aperture runs normally again. If Quicktime screen recording is run in screen crop mode the problem occurs.

    So I can't send them a screen recording. Currently I am using this method whenever I use Aperture and just dumping the recording after. Bizarre.

    Any thoughts and I would love to know if this works for you if you have the problem.

  • increatyv Level 1 Level 1 (0 points)

    Strange. So it's somehow link to graphical card driver or something like that...

    Hope this will help Apple to fix the bug. I'm thinking to move to LightRoom even if Aperture is a great product (before maverick...)

  • Red Rock Rick Level 1 Level 1 (0 points)

    Going with the graphics card idea, it may be transferring and processing memory and dumping through the graphics card VRAM.  I am not an expert but this may be why you are not experiencing the problem when you are using Quicktime FULL screen recording. 


    I am having the same type of problems when editing pictures.  I am going to start testing some of the fixes I have read here.

  • OC Lan Man Level 1 Level 1 (0 points)

    I am having similar issues as many here. When I was running Aperture on Mountain Lion I had no issues. With Mavericks I can work on pictures for awhile and then get a message that the system is out of memory. The Kernel will be using 10GB of memory. I can sometimes close Aperture and other times just get the spinning beach ball when trying to close. Once I completey quit or Force quit Aperture memory goes down dramatically. I can start Aperture and use it for awhile until the same thing happens again. I have a mid-2012 MBP with 16GB memory. Hopefully Apple comes out with a fix soon as it is extremely frustrating.