Previous 1 2 Next 25 Replies Latest reply: Nov 17, 2011 11:54 PM by Taro-71
Taro-71 Level 1 Level 1 (0 points)
After update to AP3.1 editing is become a nightmare.

Scenario:
- boot my MacPro with 24 GB RAM (64 Bit Kernel)
- start Aperture 3.1
- start working on a 20Mpixel photo (some basic adjustments)
- start applying a brushed BW adjustment

After a two minutes of intense last step (brushing) MacPro become choppy.

syslog write:

23/10/10 13.01.25 Aperture[296] Synchronous request, waiting for page to become ready
23/10/10 13.03.29 kernel (default pager): [KERNEL]: Switching ON Emergency paging segment
23/10/10 13.03.37 kernel (default pager): [KERNEL]: System is out of paging space.
23/10/10 13.03.37 kernel (default pager): [KERNEL]: Failed to recover emergency paging segment
23/10/10 13.03.52 kernel (default pager): [KERNEL]: System is out of paging space.
23/10/10 13.03.52 kernel (default pager): [KERNEL]: Failed to recover emergency paging segment
23/10/10 13.03.37 kernel (default pager): [KERNEL]: Failed to recover emergency paging segment
23/10/10 13.03.52 kernel (default pager): [KERNEL]: System is out of paging space.
23/10/10 13.03.52 kernel (default pager): [KERNEL]: Failed to recover emergency paging segment
23/10/10 13.04.19 kernel (default pager): [KERNEL]: System is out of paging space.
23/10/10 13.04.19 kernel (default pager): [KERNEL]: Failed to recover emergency paging segment
23/10/10 13.04.49 kernel (default pager): [KERNEL]: System is out of paging space.
23/10/10 13.04.49 kernel (default pager): [KERNEL]: Failed to recover emergency paging segment
23/10/10 13.05.25 kernel (default pager): [KERNEL]: System is out of paging space.
23/10/10 13.05.25 kernel (default pager): [KERNEL]: Failed to recover emergency paging segment
23/10/10 13.06.16 kernel (default pager): [KERNEL]: System is out of paging space.
23/10/10 13.06.16 kernel (default pager): [KERNEL]: Failed to recover emergency paging segment
23/10/10 13.07.05 kernel (default pager): [KERNEL]: System is out of paging space.
23/10/10 13.07.05 kernel (default pager): [KERNEL]: Failed to recover emergency paging segment

and so on...

Activity Monitor show Aperture consuming 22 GB of RAM! (and 23 of VMem)
System have all memory used(!) and 6 GB of swap in use!!

Then Aperture run in "infinite loop" one task processing image.

Quitting Aperture All memory is freed and syslog say:
23/10/10 13.08.22 kernel (default pager): [KERNEL]: Recovered emergency paging segment

Last update had killed AP3
Apple Please fix ASAP! Aperture is not a toy, is a critical tool for Pro users!

p.s. someone have an idea to rollback to previously version?

MacPro (early 2008) 8 Core 3GHz - CinemaDisplay 30", Mac OS X (10.6.4), 24 GB ram - ATI Radeon HD 4870
  • Taro-71 Level 1 Level 1 (0 points)
    Update: issue present also booting in 32Bit kernel
  • 153957 Level 2 Level 2 (485 points)
    To roll back to the previous version you will need a backup of your Library before the upgrade, because when you upgraded to 3.1 Aperture told you that it was going to upgrade the library, which then can not be used by older versions of aperture anymore.

    So you can reinstall aperture by just removing it and reinstalling it from v3 and then updating the the last version before 3.1, but as for the library, you will need to restore that from a backup.
  • Taro-71 Level 1 Level 1 (0 points)
    OK, I've isolated the issue.

    I've created a one image library with some adjustments applied.
    Image is s a 20 Mpixel 8 bit PSD Photo.

    Tried this library on a MacBook Pro C2D - 3 GB ram and the problem is immediately came up.
    MacBook sit down with memory full and GigaBites of swap paging...

    Step to reproduce:
    -- enter in viewer and select adjustments
    -- chose the brush on Black&White adjustment
    -- Brush and unbrush (alt key) over the photo for a couple of minutes zooming (Z key) in and out like a normal session.

    the machine will be choppy and, opening activity monitor, the memory used will be ~100% with a lot of swap

    If someone wanna try, here can be downloaded the isolated test library (50Mb):

    https://files.me.com/rossipaolo/g4hbbq
  • Marc Feldesman Level 2 Level 2 (295 points)
    I've downloaded the image and tried to reproduce your problems. I can't reproduce any of the memory paging, any of the thrashing, or any of the problems you report. I have the same Mac Pro, only 16GB of RAM, and the Radeon 5770 video card. I tried brushing on the B&W and my machine was snappy and was using less than half of the wired memory. I also had several other programs running in the background. It sounds like you may have a software interaction problem. That's happened to me and took me a long time to work out. The updated Aperture 3.1 with the updated ProKit runs quickly and hasn't once slowed down except when I had about 40 images loaded. Even then I never got a paging error, just slightly slower response and a few spinning beachballs. That happens in CS5 too.

    What else do you have running?
  • Taro-71 Level 1 Level 1 (0 points)
    Hi Marc,
    The problem happens with no other program running, after a fresh reboot.

    The strange thing is that my macbook pro 17" (2006) is very different machine from my MacPro but the problem is the same.

    The problem is not after two or three brushed but usually after a couple of minutes of repeating operation (think about a subject isolation, and/or using the feather on the layer mask), after a "x" number of operations, seems that something brokes.

    If you can, try the feather tool on the current BW mask, enabling the "color overlay" feature; this method bring me in that condition faster.
  • Marc Feldesman Level 2 Level 2 (295 points)
    I spent a good 15 minutes brushing, feathering, and doing all the sorts of things you might do to make a good looking B&W. At no time did my machine run out of memory, slow down, start paging. I haven't tested this on my new Mac Book Pro (mid-2010) with the Core i7 processor and 8 GB ram. How much video Ram do you have. My 5770 card as a full gig of video RAM. Wonder if that is related to the problem. I'm also using a 24" LED monitor.
  • Taro-71 Level 1 Level 1 (0 points)
    Thank you Mark for your time.

    I also have done more testing, and the issue seems to be more complicated:

    In the library I've previously posted I've added a couple of RAW file and a couple of jpeg (20Mpixel), then I have done some brushing on all, also with other adjustment, without any kind of problems.

    Then I've Lift & stamp the adjustment of the first image (the flowers) over the other photos and I've tried to BW brushing the subjects of them.

    Now, with RAW file, no problems at all, instead with jpeg the issue rapidly manifests.

    Maybe is a problem with 8 Bit images or only fortuity?

    This problem will drive me crazy :/
  • Clem Level 3 Level 3 (655 points)
    Hi Taro, I tried this on a new MBP 15" 10.6.4 with 4GB using your sample Prj with the PSD. I could see a problem similar to what you saw in 3.1 but could also see more or less the same problem in 3.0.3.
    One possible temp workaround might be to disable the other adjustments while you do your brushing? Or disable preview generation for that project while you work on it to diminish contentions.
  • Taro-71 Level 1 Level 1 (0 points)
    Hi Clem, thanks for your try.

    I've tried to disable previews in any way I know: preferences, deleting all preview, disabling flag in "Maintain previews in all projects". But when I try to edit that image, in particular the BW mask the problem reappear immediately.
    (now I've to regenerate all because are disappeared from iPhoto and iPhone... :P )

    I admit that aperture preview concept confuse me a little, maybe could be better to have a very small previews in browsing (very fast to generate an small) and a realtime regenerated full size image when choosed by the needed program, but this not is the right thread to speak to.

    In this case I can temporarely disable the others adjustments for shure, but the problem is that in a real working session this operation become very uncomfortable: think about a complex set of adjustements in a projects, enabling/disabling for minimal retouch can become a frustration...

    In my case, with 3.0.3 the problem was fixed.

    I hope the sample project I've posted can be useful to isolate the issue for a quick fix.
  • Taro-71 Level 1 Level 1 (0 points)
    problem persist also with OSX 10.6.5
  • MacRicco Level 1 Level 1 (55 points)
    I experienced the same memory problem, mainly when using brushes on large images (500MB). The brushing in itself would be ok, but feathering or moving the slider in de adjustment pane would quickly exhaust my RAM.

    In my case the 10.6.5 update seems to have solved the problem on both my systems. Will do some more tests and let you know.
  • MacRicco Level 1 Level 1 (55 points)
    Ok, it seems to a little bit more complicated. My first test was on a virgin image with no other adjustments applied; there I can brush as much as I want. The problems is still there when brushing on heavily adjusted images.
  • MacRicco Level 1 Level 1 (55 points)
    Maybe I have discovered the common factor in all of this: Zoom.

    Without Zooming-in I have not been able to break it. A large 16-bit TIFF (700MB) with almost all heavy adjustments applied (curves, HS, edge sharpen, many retouches) and then feathering and adjusting 5 different brushes, not a problem (with color overlay on!). As soon as I zoom-in and touch one of the brushes the active memory claimed by Aperture rises steeply. If you leave zoom in time, the memory curve levels of and all is well again (the memory is not reclaimed though, so yes it is a leak).

    So it seems that the problem is with the screen update in zoom-mode. Maybe they are trying something clever with only updating the visible part of the image and it backfired?
  • Taro-71 Level 1 Level 1 (0 points)
    Hi MacRicco, thank you for your trials.

    Seems you are right: I've brushed a lot the "cursed" photo without any problem, avoiding the zoom, and the problem isn't occurred.

    The only issue, Aperture crashed when I've quit, but I've no idea if is pertaining to the same problem.
Previous 1 2 Next