1 2 Previous Next 25 Replies Latest reply: Nov 17, 2011 11:54 PM by Taro-71 Go to original post
  • 15. Re: Aperture 3.1 Serious memory usage (Memory Leak?)
    Vince LaMonica Level 1 Level 1 (5 points)
    I can confirm that this is the case even with small files. A Canon RAW file of about 12MB from a Canon 40D can reproduce this problem each and every time. Fresh boot, load Aperture 3.1. Collection contains 135 photos shot Sunday, stored on FW800 ext. drive. Open an image, apply the shadow/highlights to a brush. Brush in areas on the face. No problem so far. Zoom in. No problem. While still zoomed in, use the slider on the shadows/highlights tool to adjust the shadow just a bit to the right. With Activity Monitor running, one will immediately see all memory disappear from the system and Console, within 2 seconds, shows the "System is out of paging space." and "Failed to recover emergency paging segment". The system becomes unusable. Last night it took over 45 minutes for the system to respond to a Command-Q to quit Aperture.

    My iMac has 8GB of memory, and I've disabled Spotlight as much as I can (but activity monitor still shows it taking 3.28GB of virtual mem, even though i have it set to ignore all drives and have unchecked all file types).

    When the problem happens, Activity Monitor will show my free memory at under 8MB. Yes, MB. :-O

    Adjusting the slider while the image is not zoomed in, no leak appears. I'm not using the Quick Preview feature in this case either.

    Other than zooming out, making a slider adjustment, zooming in to check, and repeating that process, are there any other work-arounds? This is quit annoying when I've got several different adjustments to tweak (in the test case above, i've only added one adjustment).

    I can send someone the sample file in case someone wants to see if their system does the same as mine.

    Also, probably unrelated, but I've had Aperture 3.1 crash many times during a session (and sometimes lose all the adjustments i had applied to the photo i was working when it crashed!). I've been using Aperture since 1.0 & use it daily; I've never seen any version of Aperture crash as frequently as I have with 3.1.

    Kind regards,

    /vjl/

    Message was edited by: Vince LaMonica - Replaced square brackets with ( and )

    Message was edited by: Vince LaMonica - Replaced square brackets with ( and )
  • 16. Re: Aperture 3.1 Serious memory usage (Memory Leak?)
    John Bertram Level 1 Level 1 (125 points)
    And I can confirm that this problem exists with even smaller files: as in the 1345x896 324KB jpg I was just working on -- practically microscopic by Aperture standards. And with NO zooming whatsoever at any time.

    But it pretty much always happens (regardless of file size; regardless of whether other apps are running or not) when I'm doing "large" brush adjustments -- i.e. brush adjustments that sweep over large portions of the image. And it's not one particular brush -- it can be Dodge, Burn, Contrast, Polarize, or a host of others.

    This was also a problem for me in Aperture 3.0.x, but if anything has gotten significantly worse in 3.1.

    And the only "solution" I've found -- when having to do these kinds of macro Brush adjustments -- is to work VERRRY SLOWWWLLLY, keep my eye on Activity Monitor's System Memory tab constantly, and then every few minutes quit and re-launch Aperture before it has the chance to suddenly freak out and go on a memory binge, hang, and then "quit unexpectedly" on its own. Hardly a satisfying workflow.

    Yet in the Inspector I can go as nuts as I want in the Adjustments pane, have Photoshop plus Pages plus Mail all running along with twenty active windows open in Safari, and no problem. It's only when I have to apply large-scale brush adjustments that Aperture seems to lose all perspective and suffer this bizarre memory meltdown.

    I desperately hope the under-the-hood Aperture folks are giving this problem serious attention (I've certainly been providing as much description as I can in the MANY automatic crash reports they've been getting from me lately) -- but would be hugely grateful if anyone has any suggestions on trying to live with this maddening Brush Adjustment Memory Drain.

    Thanks,

    John B.
    Toronto
  • 17. Re: Aperture 3.1 Serious memory usage (Memory Leak?)
    AG Kinowerken Level 1 Level 1 (0 points)
    Having the same problem here on a MBP 2.8 with 4GB RAM. Because of these issues with memory, I close out every other app when working in Aperture. I work mostly with archival monochrome stills which I've scanned as 24 bit RGB TIFFs. Aside from minor tweaks to curves, levels, etc, my primary arena of adjustments involve retouching, often upwards of 500 brush strokes, to remove dust, scratches, etc. This is all done at 100% zoom (by necessity).

    I find that Aperture 3.1 becomes agonizingly slow about 1/3 of the way through this process with lots of hanging (and far too many forced quits) and crashes. For instance, applying a 3-pt brush to a speck of dust will take upwards of 2 minutes to render whilst I sit and stare at the spinning wheel ("processing"). And as I said, the more I work on the image -- i.e. the more retouch strokes the app has to juggle in the air -- the slower it becomes. A check of the activity monitor shows massive memory loss: at one point, whilst applying a dodge brush, the system was down to 5MB of available RAM. Page in/outs are off the charts, as might be expected.

    Since what used to take a few minutes in Aperture 2 now takes hour and hours in Aperture 3.1, my workaround is to settle the tonal adjustments first (curves etc) and the create a new version from the master. From this I work on one section or quadrant of the image in terms of retouching, export as TIFF at original size, re-import (which then locks in the previous round of retouches), and then continue with next section. After three or 4 exports and re-imports, I have a completely retouched version. At that point, I lift and stamp the tonal adjustments from the original onto this new version for a final version.

    The problem with this, aside from the ridiculousness of having to operate in such a way, is that the image becomes increasingly less focused with each export/re-import. I am able to salvage this a bit by using Nik's sharpener prior to final output, but a side by side comparison with the original scan and the final adjusted version still shows degradation.
  • 18. Re: Aperture 3.1 Serious memory usage (Memory Leak?)
    cloud.rider Level 1 Level 1 (0 points)
    Same here:

    Working with MacBook with 4GB RAM, fresh reboot, no other app running.
    Using brush (brushing in highlight/shadow adjustment) on 12 megapixel image while zoomed in, then touching the High/Low tonal width sliders while still zoomed in, and RAM usage maxes out, Aperture 3.1 uses 2.66 Real Mem + 4.5 GB Virtual mem, and the wheel spins endlessly, I have to force quit it.

    Every single time I tried.

    If I relaunch Aperture, and start adjusting the sliders again, but without using brush before, then the problem does not happen (no matter if zoomed in or not). I got in the habit of first using brushes (usually works) then restarting aperture, and then adjusting levels (that also works). Combining the two in one session freaks out Aperture.
  • 19. Re: Aperture 3.1 Serious memory usage (Memory Leak?)
    LoungeHH Level 1 Level 1 (0 points)
    Same her:
    Zoom in with Z, applying sharping with brush, changing sharping values and "System is out of paging space"
  • 20. Re: Aperture 3.1 Serious memory usage (Memory Leak?)
    LoungeHH Level 1 Level 1 (0 points)
    *Your workaround does not work for me:* Applying brushes, restart Aperture, changing values of previously applied brushes or switching them on/off. If I do so, Aperture is starts eating virtual memory. Short after passing 5 GB virtual memory the "system is out of paging space"
  • 21. Re: Aperture 3.1 Serious memory usage (Memory Leak?)
    e2photo Level 2 Level 2 (165 points)
    I crash at least once a day. Not necessarily related to using the brush, but most of the time it is during brush use linked. And on one occasion, a corruption of a library so it would not open. To say the least, this is a very sad situation for a Version 3 piece of software and certainly unexpected. I am pondering my options, but I am sort of closing in on the following process. For Aperture, I keep all my images as referenced. I assume that I can do the same in Lightroom. If this is true, then I will point both programs to the same RAW images, do my work that absolutely needs to be done in Aperture since I know the program so well and begin to teach myself Lightroom. I don't know, but I suspect this will result in my migration to Lightroom, although such a decision will leave me with a huge legacy problem of nearly a decade of pictures currently linked to Aperture.

    Every night I pray the Aperture Team gets it right.
  • 22. Re: Aperture 3.1 Serious memory usage (Memory Leak?)
    Men88 Level 1 Level 1 (0 points)
    Also when I order 100 "10 x 15 cm" prints from Apple, Aperture is processing the photos beforehand. During this process around 8 GB disk space is eaten by the Swap File.

    This also occurs when using some brushes. Aperture is very sensitive, especially when using zoom/loupe. It's easy to have the computer hang.
  • 23. Re: Aperture 3.1 Serious memory usage (Memory Leak?)
    Andrea Canella Level 1 Level 1 (5 points)
    Hi everybody, i have the same problem here.
    After an hour or so of simple retouching on some Jpegs all the memory got eaten by Aperture making even the whole OS slowly.
    The only solution is to quit Aperture and reopen it, so you can have your memory back.
  • 24. Re: Aperture 3.1 Serious memory usage (Memory Leak?)
    e2photo Level 2 Level 2 (165 points)

    UPDATE NOTE-  I was having tremendous difficulities with Aperture 3 crashing on a regular basis to the point where it was nearly unuseable.  After lots of testing/evaluation and my own hardware tests, I took my machine into the local Apple Store where they did a more extensive evaluation.  They discovered a bad video board, replace it and Aperture now is working flawlessly thus far.  Several portrait session touch ups and a large wedding.  Keeping my fingers crossed, but I now believe my problems were related to hardware (video card) and not

    1. Permission repairs

    2. Use of external USB drives for library/picture management

    3. Or any of the other things that are recommended when Aperture starts to have problems.

     

    So remember, make sure your hardware is healthy!!

  • 25. Re: Aperture 3.1 Serious memory usage (Memory Leak?)
    Taro-71 Level 1 Level 1 (0 points)

    No more issues in Lion

1 2 Previous Next