Previous 1 2 3 4 5 Next 441 Replies Latest reply: Mar 10, 2010 6:38 PM by Shell Otto Go to original post
  • Anthony Brien Level 1 Level 1 (0 points)
    I'm also having a nightmare upgrading my library to Aperture 3. My library contains about 12,000 pictures, and was sized 18GB.

    After the initial upgrade of the library, Aperture is completely unusable. It also takes up so much CPU, that the entire operating system is unusable while Aperture is opened.

    I understand its normal at first for Aperture to be slow because it is upgrading all the pictures (I turned off Faces). But the problem is, if I give Aperture all the time it needs, it fails because OS X complains there is no more memory available for the application. Aperture says it's processing, but the activity window shows its always at 0 of 1201 items to process. My entire 35GB of free space on my hard drive gets completely taken by Aperture. If I kill aperture, my HD slowly comes back to 35GB of free space. If I restart Aperture, it takes about an hour to eat up all the available space and it gets stopped complaining it doesn't have memory.

    I've done this about 4 times now, and I have no idea if there's any progress being made in the upgrade. If I try cancelling the "Processing" task in the Activity window, it takes forever and never actually cancels it (it gets stuck at "Cancelling").

    I guess I'll have to pull my backup and start over again. Very very disappointed with this purchase...
  • danielhoughton Level 1 Level 1 (0 points)
    I've been sitting patiently for 24 hours while my aperture 2 library is trying to upgrade to 3. It using 52% of my 4gigs of RAM but hasn't crashed. It's still only at 10% complete!!! Whats going on apple? I haven't force quit anything but this is getting ridiculous. I have a back-up copy of my library, which is around 300gigs.
  • procksa49er Level 1 Level 1 (0 points)
    Just wanted to add a reply to show Apple techs this isn't localized to those posted so far...

    I am having the same problem. I have a MBP 17inch (Last of the non unibodies) with 4GB memory and 500GB hard drive. If I let Aperture run (after importing iPhoto Library... I am new to Aperture) It with in 10-30minutes leaves me with less than 50MB RAM and chews through 59GB of SWAP space filling it. I then get a prompt asking me to force quit unused Apps of which A3 and Finder are the only ones. Usually the processing gets thru Approx 100-150 images out of 2800 total and the total does decrement by the correct amount so it is making progress, but I have to hard shutdown / wait for the swap to clear as well as get memory back (IF it didn't freeze completely). I am down to 1800 to process but at this rate it could take weeks. APPLE PLEASE FIX THE BUG!!!
  • tomasijs Level 1 Level 1 (0 points)
    I too am excited about the new version. I backed up my library. Then proceeded with the installation of my purchase key. Upgrade went well. As soon as I tried to run after that and the faces detection kicked in, I too suffered the same issues.

    We are early adopters, obviously and have to be willing to take the risk when installing a brand new piece of software. I am a pro photographer and am just as upset as the rest of you, it should "Just Work" like everything else apple makes.

    I think it is time Apple let down the veil of secrecy and adopt the new industry best practice of allowing users, especially for pro apps, participate in a beta program to vet out these issues, so the final release is not really a beta with a unacceptable memory leak. I find it hard to believe this did not show up in testing.

    It is all about perception, and right now the clock is ticking on Apple Aperture 3.0. Let's hope we get a fix before the end of the week.
  • Obi Just1n Level 1 Level 1 (10 points)
    Same thing here.

    I left it on over night and came to a completely unresponsive system. First time ever.

    I have a MacPro with 5 GB ram. Aperture keeps allocating memory over and over to the point that my disk runs out of space due to the size of the swap file (150GB). During this time the computer is completely unusable.

    This was trying to upgrade my A2 library to A3.

    I'm now trying a project import from my A2 vault(since I can't restore from my A2 vault)
  • lukelucas Level 1 Level 1 (0 points)
    alrighty, so i am currently in touch with Apple through a couple of channels. one channel found me via this thread, so obviously, there is some notice being taken.

    the other was is a phone call i made this morning. we ran through a whole bunch of steps to ensure my disk was fine (it was) and now we're experimenting with a couple... uh... experiments. we'll see what happens.

    keep the stories coming, folks! Apple knows there's a problem here and they need to keep hearing your voice!
  • demoneyes Level 1 Level 1 (60 points)
    Hi everyone,

    Don't give up just yet. This is frustrating, but it appears to only affect importing. Once the images are imported, things are running very smoothly.

    I imported about 300 RAW files, and let it just sit and churn for a few hours. I did not attempt to use the computer during this time. It did eventually finish, and the images were properly imported. Apple is paying attention and working on a solution. I've been contacted and am sending data directly to them to help them diagnose the problem.
  • lukelucas Level 1 Level 1 (0 points)
    300?

    is that all you have, or were you just doing a sampling? because honestly, 300 is a pretty small amount, so i can understand why you may be having an easier time than most of us.

    ALSO...

    one of the experiments we're running is taking one of my smaller, non-upgraded libraries and and upgrading it to A3 specs on a different computer (that wording is confusing, i know). so i took our still-in-version-2.1.4 Aperture library from our home iMac and just finished importing it into Aperture 3 on my office Mac Pro. this is a dual-core 2.66 MacPro with 16gb RAM.

    it seems to actually work alright, but look at the activity monitor:

    http://twitpic.com/12fzmm/full
    http://twitpic.com/12fzqp/full
  • minimoto71 Level 1 Level 1 (5 points)
    Aperture 3= Slooooowwww Application. My god, so much time waiting for this upgrade and now it doesn't work as expected. I've got a Mac Pro 8 Cores at 2,66 GHz with 8 GB RAM memory and it's just a nightmare to work with this app. Very very slow to do anything, from import pictures to correct then or just opening or closing ( and just working with a fresh trial library, I don't want to think what it can happen with my 25.000 pics library if I import into A3.... ). It's amazing as Jobs use to say but in the worst meaning of that word. I have been an Aperture user since version 1 but I'm afraid this is going to be the last I'm going to try. Hello, Lightroom, bye bye Aperture.
  • Matthew Bergsma Level 3 Level 3 (600 points)
    Odd, I had the opposite reaction on both my mac pro 2.8 and my mac pro 3.2.

    Did you turn off Faces, GPS, and automatic preview generation?
    Did you open the activity window to see what is going on in the background?
  • Matthew Bergsma Level 3 Level 3 (600 points)
    It is a bummer that this is still required, but PEOPLE THE OLD OPTIMIZATION RULES STILL APPLY. use the activity window to see what is going on in the background!!!

    #1 turn off automatic preview generation!!!
    #2 turn off Faces
    #3 Importing is just as fast if not faster than aperture 2.

    But with automatic preview generation and a fragmented hard drive, you are asking for trouble...

    Also, for those who haven't upgraded yet, I recommend relocating your masters outside of the library first, and "updating" by using File->import library... This will keep your version 2 library intact, and give you a clean aperture 3 library.
  • Rshrieve Level 2 Level 2 (310 points)
    Well, you all have convinced me to wait until these "upgrade" issues get cleaned up before I switch to A3.

    Sorry for all your trouble but thanks very much for sharing.

    Rich
  • lukelucas Level 1 Level 1 (0 points)
    so maybe the problem really does lie in the size of one's library. as per the experiment, i imported & upgraded a smaller, non-upgraded, 2.1.4 Aperture library onto both my MBP and my work MacPro. and ya know what?

    they both run beautifully with the smaller library.

    so, maybe the problem has been found (on my end, at least), but we're nowhere near solving it.
  • danielhoughton Level 1 Level 1 (0 points)
    I have to agree with that. The problem is defiantly added to by the size of the library. My Aperture 2 library contained over 300,000 images. It's pushing along with the upgrade, (currently updating thumbnails) and is still only at 20%. It's been going for 29 hours.
  • lukelucas Level 1 Level 1 (0 points)
    HOLY SWEET BABY JESUS.

    i woulda' ripped my eyeballs out by now.
Previous 1 2 3 4 5 Next