Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

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

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)

Posted on Feb 9, 2010 8:56 PM

Reply
441 replies

Feb 12, 2010 11:18 PM in response to lukelucas

I wish I could say that turning off Face Detection did the trick for me, but alas it seems not. Ap3 is hung up on "processing" four remaining items (whatever they may be) and hasn't seemed to make any progress after a few hours, leading me to believe even if I let it run all night it won't complete the job. (We shall see.) And all this for only 2K images. I hate to think what it would be like for my other library of over 13K images.

Arghh, to say this has been a frustrating exercise in futility wouldn't begin to describe my disappointment.

Feb 13, 2010 1:51 AM in response to lukelucas

Im having similar problems If not identical, so much so that I have stopped trying to open Aperture 3. I have tried to open my version 2 but it comes up with a message stating that I have a newer version then shuts down. I have a couple of aperture 2 vaults which I backed up before doing the upgrade and I was hoping someone can tell me how I can gain access to them and get Aperture 2 up and running.
I've given up on Aperture 3

Feb 13, 2010 1:57 AM in response to k3let

OK since I had a rant earlier, only right to update things and say A3 now seems to be working (touch wood).

My solution was to turn off faces, and to stop the laptop whenever the free space got close to 20GB. Re-boot and it cleared the Virtual memory so gave me back 60GB. Now with 80GB I would re-start Aperture. Repeated three times over the ENTIRE day, and voila - things seem to be done.

Your mileage may vary. Still think a sucky process, most un-Apple like.

Feb 13, 2010 4:08 AM in response to lukelucas

Just to balance things out, I'll report that my upgrade went flawlessly on 30k+ images, with a managed library on a quad 2.66 Mac Pro, 16GB. Of course, I didn't leave it to chance, so I cloned my library beforehand. Remember everyone, backups are THE most important thing in your life.

I did however have several problmes last year when I imported a batch of 15k images into A2. There was a single corrupt file that hung on the thumbnail build. I do recommend if you're having problems with the Library update, trash the library, make a second backup and reimport project by project.

Good luck, and remember this is a point release and we're all early adopters, so we take a risk that there will be bugs, naturally.

Feb 13, 2010 4:32 AM in response to lukelucas

Hi, my A3 has been processing only about four thousand images for hours but now it is hanging. It says processing 0 of 551 images for over two hours, nothings changed. What should I do here??

Also as with many others my iMac has been brought to snails pace, took me ten minutes just to select force quit do to the shear lag of the computer!

Feb 13, 2010 5:16 AM in response to lukelucas

I finally got to a point where all images were processed and Aperture finally started working correctly. I could even turn Faces back on, and it worked great.

But eventually I seem to come back to the memory leak problem and Aperture becomes unbearably slow again. Even if I quit and restart it. I noticed the best way to get rid of the problem is to turn off Faces again, quit Aperture (not Force Kill), and restart Aperture, and turn Faces back on. But I've had to do this about 4 times already. Also sometimes restarting Aperture just fails with no errors whatsoever. You see the Aperture icon bounce in the dock, and then it resets as if Aperture is not running anymore. After a few tries, it eventually opens. Using the 32-bit mode definitely helps keep your system stable, even when Aperture has the problem. I get crashes too, which at least we can send to Apple.

So the problem might not just be an initial import problem, it seems to come back afterwards too.

Feb 13, 2010 6:17 AM in response to Anthony Brien

I turned off faces in Preferences and allowed the computer to run all night. The processing finished and A3 seems to work fine at this point.

However, I have noticed that it does take a little longer to load an image then A2.

All in all, it appears that faces is the culprit. If you have 10,000 images (I have more then that) and are allowing A3 to try and match all possible combinations of faces, in that many images, is a daunting task.

Thanks, but faces is not something I need or want. Especially with it, seeming, effects on the ability to use A3 effectively.

Feb 13, 2010 8:38 AM in response to auro

Yeah, I'd like to know that, too. When I try Aperture 3's "Get Info," I don't appear to have the ability to select 32-bit like I do with other programs. By the way, I actually called Apple Support on this matter. They were unable to help and have sent the problem along to their "technicians" for review and a possible solution. The guy I spoke to seemed to think the problem was with Aperture 2, a corrupt file or files, that's also discussed above.

Feb 13, 2010 9:04 AM in response to robogobo

This 32 bit issue

Do you mean boot OSX in 32 bit mode as opposed to 64 bit mode, default on OSX is 32 bit

Are you sure you are not doing the get info on the Aperture 2 icon rather than the Aperture 3 icon

Finally if your machine cannot boot in 64 bit mode then all apps will be forced into 32bit mode - it may be that in such a case the tick box does not appear.

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

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.