Skip navigation
This discussion is archived

Aperture 3 hanging... and hanging... and chewing...

86826 Views 441 Replies Latest reply: Mar 10, 2010 6:38 PM by Shell Otto RSS
1 2 3 ... 30 Previous Next
lukelucas Calculating status...
Currently Being Moderated
Feb 9, 2010 8:56 PM
was totally stoked about upgrading today. now i'm kicking myself in the pants for doing it so quickly.

when i came home for lunch, i installed A3, typed in my purchased Upgrade serial, and then allowed A3 to upgrade my old A2 library. obviously, this was gonna take awhile, so i left it running whilst i went back to the office. when i returned home, i discovered my MBP had actually frozen. ok, that was weird. i had to do a hard shut down (hold down power button) and then reboot. everything comes back fine, i reopen A3, and its just processing "files." i let that go for about 15 minutes, come back, and the MBP has just sloooooowed to a crawl. i mean awful. it was like being at a concert: beach balls of death EVERYWHERE.

i didn't want to, but i had to force quit A3 to do anything else. so i did that, did a normal Restart, and then reopened A3. still processing, same chain of events. i mean, it was terrible.

so finally, FINALLY, i get down to the last 12 "files" or "items" or whatever, and A3 seems to be really stuck on these last 12. it'll just sit there and churn away whilst eating up all system resources and giving my BBODs whenever i move the cursor around.

so... what's going on here? i've tried repairing the database as outlined in the recently update Aperture manual (to no real end; didn't fix anything), and my next step, i suppose, is rebuilding the database. is anyone else having a problem like this? i've seen lots of folks having fairly terrible times with the move, but nothing quite like this. i've a fairly large library (not really giant by any means).

so: help!
2.26gHz Intel MacBook Pro, Mac OS X (10.6.2)
  • col4bin Calculating status...
    From all that I have been reading, it sounds like the only happy folks after installing Aperture 3 are those with the most powerful MacPro's. This is very disappointing. There could have been 2,000 new features but they are useless if the application runs so slow. Beachballs belong on a beach....not in a professional application.
    MacBook Pro 15.4" C2D 2.8GHz 4GB/500GB, Mac OS X (10.5.7), 23" ACD
  • demoneyes Calculating status...
    col4bin wrote:
    From all that I have been reading, it sounds like the only happy folks after installing Aperture 3 are those with the most powerful MacPro's. This is very disappointing. There could have been 2,000 new features but they are useless if the application runs so slow. Beachballs belong on a beach....not in a professional application.



    Nope. I've got a Mac Pro and 6GB of memory and suffering the same problem. What's happening here is during the migration, Aperture is using up all available memory, and OS X beings swapping processes to the disk. That is why things are slowing to a crawl -- and us Mac Pro users have the same problem. People with lots and lots of memory might be ok, though. Amazing that 6GB doesn't qualify as "lots and lots" anymore.
    1st Gen MBP, Mac OS X (10.5.5)
  • demoneyes Level 1 Level 1 (60 points)
    That's a good idea. I've been using File->Import. I'll try it the other way.
    Mac Pro, Mac OS X (10.5.5)
  • demoneyes Level 1 Level 1 (60 points)
    Eek, yeah this might be too much work. I did find another bug, though. I went to File->Switch To Library and selected my Aperture 2 library. It said it would have to relaunch the application, to which I agreed. It came back up with my Aperture 3 Trial Library. Does it every time... soooo....
    Early 2008 Mac Pro (6GB/3TB), Mac OS X (10.6.2)
  • stevenbrown Level 1 Level 1 (5 points)
    Same here - 2yr old Alum iMac, 4G RAM, intel dual 2.4GHz, 250Gb free on boot drive.

    I had to fully force-quit two times so far. Brutal. Within less than a minute, A3 has gobbled up 95% of RAM (whatever RAM's available: 4Gb minus whatever the sys & finder use).

    I was able to get in and disable faces, thinking that would reduce the load some. It fully locked up, mouse & all, after that, too. Now faces is off, and as soon as the app opens (after "repair lib" each time, just in case), I jump to the activity window, select the one "processing 1500 items" activity, and try to pause it/cancel it.

    That's where I am, FWIW, it looked like it was gonna lock up again (SBBOD, can't switch to finder, can't app swx with cmd-tab)

    It's been quite a few years since I've had any app, let alone an apple one, repeatedly break the everloving snot out of a well-maintained mac. (maybe ProTools cards & SCSI drives on the Quadra 650 in 1994? lol)
    macbook air 1.8G core 2 duo HDD, Mac OS X (10.5.6)
  • demoneyes Level 1 Level 1 (60 points)
    Steve, I agree. I have no problem with the software taking advantage of the hardware. By all means, please do...but as a software engineer myself, this is clearly a bug. A really bad one, too. And how the $#%! did it get through QA? Seriously people. Any real testing should have caught this.
    Early 2008 Mac Pro (6GB/3TB), Mac OS X (10.6.2)
  • stevenbrown Level 1 Level 1 (5 points)
    Update - fully locked up again (of course each time I start in safe mode, run disk utility, restart, run it again, then start aperture with cmd-opt)

    I'm grabbing a parachute and jumping out the 'plane - bailing. Glad I don't need to make money with my pictures - I'll wait for a fix, lol.

    Geronimo!
    macbook air 1.8G core 2 duo HDD, Mac OS X (10.5.6)
  • stevenbrown Level 1 Level 1 (5 points)
    Whoa, didn't mean to be so cavalier about not using mine to make money, lol. I'm confident that Apple devs are working late or being called in to fix this - I'm praying for for no data loss for myself and you all.

    Business or personal - pictures are important. Come on Apple!

    --@demoneyes: too right - agree totally.
    macbook air 1.8G core 2 duo HDD, Mac OS X (10.5.6)
  • demoneyes Level 1 Level 1 (60 points)
    No prob, Steve. I didn't think you were cavalier. I'm stuck now because I was evaluating Aperture 2 and hadn't yet purchased a license. Now A3 doesn't work for me at all. I'm not going to spend $199 on "old" software, so what do I do? Guess it's time to try out Lightroom...
    Early 2008 Mac Pro (6GB/3TB), Mac OS X (10.6.2)
1 2 3 ... 30 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.