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

Level 1

7 points

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

441 replies

Feb 10, 2010 1:32 PM in response to lukelucas

lukelucas wrote:
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.

Oh, I know 300 is a very small amount. I just started using Aperture 2 a few weeks ago when I got my 7D. I hadn't even purchased a license yet because I was waiting to see if A3 was coming out soon. There were rumors, so I was waiting it out.

However, given the circumstances, even 300 images is proving to be difficult.

lukelucas wrote:

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.

I'll be doing the same thing. My only other machine is a first generation Macbook Pro with 2GB of RAM. Should be interesting.

I think your activity monitor screenshots are fine. With 16GB memory, you using less than 20% for Aperture. I assume you have a Late 2007 Mac Pro, with 2 dual-core processors? You can't use >200% CPU with only 2 cores. Honestly, I think your system was handling things just fine. The memory probably made a big difference for you.

With only 6GB in my box, I had Aperture using >4GB at certain points. That doesn't leave much for the operating system and other active processes to work with.

lukelucas Author

Level 1

7 points

Feb 10, 2010 1:36 PM in response to demoneyes

yeah, i had counted on the Pro handling things alright, if only because of the sheer amount of RAM.

that said, both the Pro and the MacBook Pro handled the same, smaller size library just fine. i'm about to try and import my old 2.1.4 library that's 70+GB large and see how the Pro handles that (since it was the original trouble maker).

and dude, congrats on the 7D. we've had one for about three months now and i LOVE it. its a perfect second-shooter for our 5D Mark II, and it takes some super beautiful 1080p video.

Feb 10, 2010 1:38 PM in response to danielhoughton

Just out of curiosity, what size is the library? And is it referenced or are the masters in the library? Why do I ask? I've only got around 25,000 images and my library is pushing 500GB. I've been concerned it was getting too big and thought of splitting it up. But if you can function with a library your size, I'll stop worrying!

Feb 10, 2010 1:42 PM in response to Denny Granger

The size of the library is around 300gigs. All of my masters are referenced on a 4TB drobo. I limit the size of my previews to keep things moving faster so thats why the library file is small for having so many images.

Feb 10, 2010 1:49 PM in response to danielhoughton

Thanks.

I never had the nerve to put my masters on my Drobos (I have 2 Pros and an S) but use them strictly for backup as I've had some earlier problems. Since I started with Aperture 1.0 which didn't have referencing, I never did start using it - wish I had. Maybe it's time to do so.

If you are at 29 hours, I'll plan on not using my machine for a week or so and let it do it's thing 😉

SLS

Level 2

355 points

Feb 10, 2010 2:30 PM in response to procksa49er

I see from your configuration description that you are on Leopard. Is that correct? I ask because the config says 10.5.7, but the current Leopard is 10.5.8.

The behavior on Leopard is likely to be quite different than on Snow Leopard (in part because Aperture can run in 64-bit on Snow Leopard).

Also, is your iPhoto library from iPhoto '09 or from a previous release? If you turn off Faces, does the processing experience improve at all?

Thanks.
--SLS

Feb 10, 2010 3:07 PM in response to SLS

Add me to the list too. I have a MBP, but I put this on my Mac Mini 2ghz core 2 duo with 4gb of DDR3 memory. I have my iphoto library on my external drive. I didn't like Aperture 2 cause of lack of faces and places support so I held off. But now when I imported, just like all of you, it killed my computer. Of the 65 gigs on my internal drive remaining, after 50 min of working on "processing" I am down to 30. I had to force quit cause it also went nonresponsive. I don't have any other apps on in the background. I hope this gets fixed soon. I can't use it at all.

SLS

Level 2

355 points

Feb 10, 2010 3:28 PM in response to MagicMacMan717

Were you upgrading an iPhoto '09 library or a previous version?

Does turning off Faces in Aperture avoid the problem? (it's not a solution - just troubleshooting)

Thanks!

Feb 10, 2010 3:30 PM in response to lukelucas

I have the same problem: after importing my old library (38GB), Aperture 3 uses up more and more memory. That causes it to swap. Virtual memory grows by about 10 MB per second. The system gets slower and slower with all the swapping until the hard drive is full and it freezes.

I have analyzed the process using the activity monitor. What looks strange to me is that one of the threads has an unusually deep call stack. It is hundreds of levels deep and contains mostly calls like XTCacheStore, XTCacheFactory, DGImageBackedImageProvider.

Feb 10, 2010 3:31 PM in response to demoneyes

Now Aperture 2 and 3 crash instantly, I get this from the crash-log;

Dyld Error Message:
Symbol not found: _OBJC_IVAR_$_NSProgressIndicatorPrivateData._drawingWidth
Referenced from: /System/Library/PrivateFrameworks/ProKit.framework/Versions/A/ProKit
Expected in: /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit

Feb 10, 2010 4:39 PM in response to travelboy

I observed the same deep call stack, too. I forwarded that information to the individual from Apple that has been in contact with me.

lukelucas Author

Level 1

7 points

Feb 10, 2010 4:42 PM in response to lukelucas

Apple is actually sending me a hard drive to copy my library onto and send to them for testing.

o.O

yeah, i dunno either. i'm willing to comply so long as it helps the masses!

Feb 10, 2010 5:47 PM in response to Anthony Brien

I tried importing my Aperture 2 library instead of converting it, and it seems to work much better. It finished importing 12,000 pictures, and now it's processing them slowly, but Aperture (and the entire system) is actually responsive.

So if you are having the out of memory, or VRAM grabbing all your free HD space, you might want to try importing your old library instead of converting it. To do so, rename your old library, start Aperture 3, and it will create an empty one, and use File > Import Library/Project and pick your old library.

Feb 10, 2010 6:02 PM in response to Anthony Brien

Anthony Brien wrote:
I tried importing my Aperture 2 library instead of converting it, and it seems to work much better. It finished importing 12,000 pictures, and now it's processing them slowly, but Aperture (and the entire system) is actually responsive.

So if you are having the out of memory, or VRAM grabbing all your free HD space, you might want to try importing your old library instead of converting it. To do so, rename your old library, start Aperture 3, and it will create an empty one, and use File > Import Library/Project and pick your old library.

Anthony, that's exactly what I did and I ran into problems. Interesting that it worked well for you.

Feb 10, 2010 6:17 PM in response to lukelucas

Same horrible experience with Aperture 3. The first attempt to upgrade my 256GB Aperture 2 library failed after around 7 hours. Got the pop-up window saying that I needed to kill some programs because I was running out of memory. Free disk space was around 80GB when I started... The system became unresponsive for a couple of hours so I had to do the hard shutdown.

After finally upgrading the library on the second attempt Aperture 3 would spin out of control at random times using up all system resources making the entire system unusable. Hard reboot.

I've rebuilt the library multiple times, rebooted, and tried everything I could think of.

I'm giving up and going back to Aperture 2. Maybe they'll fix the problems in a few weeks and I'll try again.

My excitement and rush to upgrade has turned into bitter disappointment. I wanted it to work so bad that I have wasted the better part of 2 days and almost half the night trying to get this to work.

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