Previous 1 2 3 Next 441 Replies Latest reply: Mar 10, 2010 6:38 PM by Shell Otto
lukelucas Level 1 Level 1 (0 points)
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 Level 1 Level 1 (0 points)
    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.
  • demoneyes Level 1 Level 1 (60 points)
    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.
  • lukelucas Level 1 Level 1 (0 points)
    really? i just don't get that, then. i know what the "minimum" specs say, but i've a 2009 MBP and 4gb of RAM sitting in here, certainly nothing to sneeze at. hm.

    i called Apple this afternoon with a relatively stupid question (not about this, though; this question was pre-debacle) and we got to talking about the update/upgrade process and i'm remembering him suggesting importing projects one at a time, instead of migrating. anyone tried that?
  • 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.
  • lukelucas Level 1 Level 1 (0 points)
    wish i had more time to stay up and get after it. as it is, exporting projects is gonna be a hassle considering how many i have and will be a "let it run overnight" deal. if you do this, keep us posted on the outcomes.
  • 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....
  • 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)
  • lukelucas Level 1 Level 1 (0 points)
    i deleted the original debacle plagued A3 library and am redoing the migration, sans whatever A3 update magic that little checkbox allows you to do. i hate to leave it running overnight for fear of something going terribly awry, but we'll see. backups, people!
  • lukelucas Level 1 Level 1 (0 points)
    yeah, that's the weird thing for me, too: i'm no newbie to Macs (since 2002) and this is the first time i've had this much trouble with any Apple-branded app. its the most bizarre thing. i want to believe Apple really tested and restested over and over again because they knew Adobe was eating their lunch with the impending Lightroom3 release, but this seems to not be the case.
  • 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.
  • lukelucas Level 1 Level 1 (0 points)
    and see, the thing with us is that my wife and i run a photography business, so we've been watching the way LR3 was just killing A2, holding out hope that A3 would squash any desire to switch to LR3 or just find a whole new workflow. if this isn't fixed quickly, its back to the drawing board for us.
  • 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!
  • 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.
  • 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...
Previous 1 2 3 Next