Aperture 3.2 upgrade (from 3.1.3) crash continuously

As I'm a hobbyist who hates iPhoto I'm going to stick to what i have, viz 3.1.3. Thanks for your help.

Helen

I just opened Aperture for the first time since doing the upgrade and I am having unresolved crashes as you all state. I have run all the appropriate library rebuilds etc to try to fix. I am unable to use the software at any level. Apple please fix your update issue.

Hi All,

I was also having issues with Aperture 3.2. In the site ApertureExper.com they suggested removing two files

http://www.apertureexpert.com/tips/2010/11/5/aperture-library-not-showing-up-in- ilifemedia-browser-possib.html

Those two files are:

• iLMBAperture31Plugin.ilmbplugin
• iLMBAperturePlugin.ilmbplugin

Located in: Macintosh HD / Library / Application Support / iLifeMediaBrowser / Plug-Ins /

They are left overs from 3.1 causing numerous other issues. It may be worth removing those files to your desktop then restart Aperture. Be sure to run Permissions as well.

Hope that helps you. Oh, by the way, do send feed back to Apple at http://www.apple.com/feedback . Apple provides these forums for user to assist users, Apple does not reside here.

Cordially,

RicD

I'll just add my voice to the chorus!

Aperture 3.2 for me is not crashing exactly. It is behaving very badly though and is in need of a smack!

Every time I open it now, it spends 5 minutes "processing" and any attempt to use it in that period results in "not responding".

I tried to back up a vault - ended up hanging for 3 hours and I had to kill it.

Imported some short Nikon D3s movies shot with a client last week - just a banded green/red/black mess and no ability to do anything with them - clicking on them just does nothing. Opening them from the camera card direct in Quicktime and they play just fine.

This is just a complete mess, Apple! Where's SJ when you need him? 😟

This didn't work for me, however I was able to move further along.. but I'm putting the files back and waiting for Apple to speak up

Could be another issue, but yesterday I posted on the mac app store a negative review that you shoiuld not upgrade to 3.2 if your machine is more than five years old (ie MBP core duo or older). At the moment I am not able to go back into the App Store - perhaps there is a tech issue or perhaps I am no longer welcome!?

Don't get to parinoid I just tried the App Store ad it's not coming up fro me either.

And I never have a bad word to say about Apple 😉

Weird, my newer imac it works no problem (3GHz intel core i3 running 10.7.2), but my older one (2GHz core duo, running 10.6.8) it's crash, crash, crash. I've tried all the solutions people post, but it's still crashing on the older one. I guess i should count myself lucky that the working one is the one i use most. I will say though that i've been able to open the same libraries on the working one. If that helps narrow down the cause, it doesn't seem to be in there that is messing with it.

Did all of that, no avail. Nothing works. Tech support has thrown up their arms and said, "Wait", were waiting for a solution from the software engineers. OK, Were waiting.

New development on my end. I can't import a image. Aperture Quits. So I'm dead in the water. Been through all of various combinations of fix, and nothing works. Didn't have these issues with Aperture 3.1. I would prefer to stay with the Aperture program. I was able to work seamlessly with it. I need to have this issue resolved soon. I can't stay on with this situation. It's getting close to having to move on with another program. If we could just hear an official announcement, that the problem is recognized and is being resolved, but nothing. I'm not one to rub salt in a wound, but Wow, what's going on?

I seem to have a problem not mentioned here.

My system is 'processing' the same 26 images every time I open Aperture.

It takes 5-10 minutes each time and the system is unavailable for use within that period. Just won't respond.

Was fine before the 'upgrade'!

Anyone have an idea how to stop that? I have done all the usual library maintenance to no avail.

So 26 images when you start up Aperture is in the processing mode all at the same time?

My symptom is now consistent:

Everything works accept; Can't load a Tiff file. Can't import a Tiff file.

Jpegs fine. In fact I think the Jpegs load faster since the upgrade!

Tiffs seem to be a foreign substance to the 3.2 upgrade

I'm tempted to delete the Tiffs from the library, and reload them from the Master folder on the desktop, but some advice in the discussion say's no ! Don't. Unless I've mis-interpreted.

I don't know how to do that anyway. Seems logical enough, but that's not in my usual path of import. So if anyone out there knows that it's ok to delete from the library, and re-import, please let me know. I could be angsting over here for nothing. Got optimism at work here.

As a pro event photographer who's relied on Aperture since version 1.0, I'm pretty adept at resolving issues, but this one's got me stumped. I suspect that the problem lies with OS X 10.7.2 rather than Aperture, as I started having crashing issues with Aperture 3.1.3 right after I upgraded to 10.7.2. I then upgraded Aperture to 3.2 and was able to rebuild and work with one of my two main libraries, but now I'm having the same trouble with my other library, even after repairing & rebuilding with Ap 3.2. I've been working on this library all day today, importing, rating and adjusting 1100 photos from a job, but when I tried to export some images to Zenfolio via the plugin, Aperture just hung. I quit it (regular quit, not force), and now Ap crashes about 10 seconds after I launch it with this library. Major drag. Did nobody at Apple test this stuff? For the time being, I'm going to create a new library for each new project so that I don't have to wait for my 60,000+ image library to rebuild every time there's a problem.

Saw your suggestion. Looked at it. There are no plug ins in file here. Wish there was. I would have tried it. I also couldn't find Macintosh HD. All leads after that though. Again, after iLifeMediaBrowser, no plug ins available for deletion.

I'm continuing to hunt for solutions. We're on day 12 with this 3.2 crash thing. Still can't import fresh images. Still can't get an image other than thumnails with Tiffs. The jpegs act normal. 3.2 seems alergic to tiffs.

Is there any word as to a lead, or solution, a confirmation of the issue from Apple. I feel like Tom Hanks, on the island in the movie, Castaway.

You do relaize this thread is about 3.2 not runing on Coe Duo processors. Therer is no solution unil and if Apple comes out with a patch to make 3.2 work on Core Duos. The only thing you can do until then is to roll back to 3.1.3.

If on the other hand you have a Core 2 Duo or later processor and are having troubles you should start a new thread.

For what it's worth, I posted in a separate thread but with a lot of the same issues.

2009 iMac Core i7, 10.6.8

Aperture crashes on Launch.

Tried all the tricks, removed Aperture, reinstalled, upgraded to Lion, all the DB first aid. No luck.

Anyway, I got a polite email from Apple about it today asking for more specifics so they can attempt to reproduce the problem.

Here's hoping they get a fix out soon.