Aperture 3.2 upgrade (from 3.1.3) crash continuously

I have a solution that fixed mine, hopefully this will do the same for someone else:

I got this fix from Nik software support team:

Then:

- check your system for duplicate fonts

- check your system for missing system fonts Arial and Times New Roman, especially when using Suitcase or FontExplorer

- then perform a "Repair permission" procedure, using the disk utiltiy

- Then restart your machine

AND SURE ENOUGH for some reason when I went into the system fonts Arial and a few others were disabled! They showed as light grey with "off" next to them. So I selected all the fonts, right clicked, and selected "enable". Now everything works great, but I have no idea how these fonts got disabled in he first place!

Hope his helps!

Well, finally I have Aperture 3.1.3 up and running again. I uninstalled everything, reinstalled 3.0 from my DVD, updated it to 3.1.3 from the Apple aperture downloads page, launched it and watched it crash like a russian fighter jet at an air display. Again, and again, and again.

This was getting tedious so I did the 'command-option-double-click-on-library' thing to launch Library first aid, and finally, having been forced to run all three scripts, finally, having let the First Aid rebuild my library (which, TBH didn't take long considering there's 60k+ images in it) it now works again. Hallelujah! I've got a brace of 'Recovered Folders' in the library pane now, and they contain various images from various projects. Not really sure why they ended up in there, but there they are, and I'm happy because Aperture 3.1.3 is doing its thingo again.

Phew. Nightmare over. I hope.

I love the way Apple's forum software redacts the word *****. A jet engine ***** in air. My vacuum cleaner *****. Suckerfish suck. My little boy ***** his milk in through a straw. Let's see what happens with all that sucking.

This is really getting ridiculous now. A brand new installation of 3.1.3, with some photos imported into a NEW library with nothing else in it, crashes just the same as 3.2. Oh, Apple, what have you done?

Anyone got any ideas as to what the heck I can try next? Total system reinstallation? Axe through iMac? Is this really the death of Aperture for me?

I'm still waiting for Apple to address this issue, I took into consideration the release of the new iPhone 4s and the memorial services for Steve Jobs.....

I am really surprised that we haven't heard anything stating apple is trying to fix this bug.. Aperture is being used by professional photographers! It's about the integrity of the software.. not whether you have your images backed up or not.. As most of us here I am very disappointed with Apple regarding this issue.. As a professional I really have no other choice but to seriously consider Lightroom.. Not to mention not being able to send customer service an email and getting a response.. That my latest rant .. Keep sending the bug reports into apple 10 a day or more

Dan,

Did you remove the left-over files pertaining to Aperture in the following locations?

~/Library/Application Support/Aperture

~/Library/Preferences

~/Library Caches

/Library/Application Support/Aperture

/Library/Caches

Removing those files prior to re-installing Aperture gives you basically a clean install of Aperture (other than some hidden files which typically don't need to be removed). Placing the files in a temporary folder on the desktop is the normal recommendation and then trashing them if the problem is fixed.

The Application Support/Aperture folders (in both the ~/ and / directories) may contain any plug-ins you installed, so you may need to re-install later after you have verified that Aperture is performing as expected.

The bit about moving the user created presets, keyword lists, etc. at the link below outlines the process for moving contents of one of the Application Support/Aperture folders:

http://support.apple.com/kb/HT3805

Note - I believe there are a couple of third-party plug-ins that place the plug-ins in a different location, but I do not remember what their names are for sure - I am thinking the Topaz series may use their own folder when not using the Photoshop plug-in version.

If you are running a Core2 Duo or newer processor, then I suspect a corrupt file, cache or a bad plug-in based on your description of the Aperture re-install. 😉

Thanks Corky. I did get rid of some of those. But I'll do the whole shebang when I'm done with my second total system restore of the day. Probably best not to ask :-) I'll let you know if I'm successful or not. Cheers.

Well, I've done system restore, deleted all plists and caches, reinstalled aperture and updated it to 3.1.3 and it still doesn't work. I'm going to try one more brand new library using the Wyoming images on the DVD and it still doesn't work then the only thing I can think of is a complete brand new system as well. Oh joy. Admittedly I haven't done that for a couple of years but I dread it as I've got to go through evil Adobe's licensing nonsense to set up CS4 again. Pooh.

Dan,

Remember to use Disk Utility to run the 'Repair Disk Permissions' after you restore and install Aperture.

I noticed on the installs I have done that there are 3 framework files that have the wrong group permissions (80, instead of 0) after installing AP 3 on OS X 10.7.2 which need to be fixed by Disk Utility. 😉

There is a glimmer of light in the darkness... It now appears that an image from my last wedding shoot may be the problem. I've got rid of my last test library that comprised only that shoot and am now making a new one with a fresh import from the cards. Thank goodness I hadn't deleted them already! So far so good anyway. :-)

All fixed. In theory I should be able to go back to my old library too, as all my masters are referenced and I've deleted the 2 corrupted images. Phew!

Oh and thanks for your help Corky, much appreciated.

Nothing works for me either. Cannot even repair ANYTHING- get as far as 98% then goes down. This frankly is CRAP-----

Mine crashes at 98% too.

Well, at least I ordered a new 17" Core i7 MBP to replace my creaky ol' 15" CoreDuo MBP. Should be golden, then.

Still, it would be nice if Apple finally addressed this issue.

Thanks for the suggestion. Didn't work for me though. I removed some duplicate fonts, Arial and TNR were enabled, fixed permissions, restarted, but still Aperture crashes.

This is taking way too long, Apple. It's supposed to be a professional application, for people who need this for their jobs. This is taking for over a week now and that's totally unacceptable.

😠