Aperture 3.2 upgrade (from 3.1.3) crash continuously

To be fair though, the title of the thread merely refers to crashes in general, not those caused by having a particular chipset.

True but if you read the first few posts you'll see that that was the OP's problem.

I have decided I need a new machine so I can run aperture 3.2 (as it crashes on my core duo laptop) my ideas is/was to buy an 27 inch iMac so I can use that in the studio and my 17inch MBPS on location. However as 3.2 uses a different library to 3.1 - i would not be able to share libraries between the SL and Lion machines! I wonder if there is an answer to that?

How can apple not be aware of this issue, the automatic bug reporting system should be enough. I'm attempting to start aperture at least once a day so apple gets a report.. Also I have paid plug-ins for aperture that I am unable to use do to the 3.2 bug... Has there been an official bug report from Apple? I'm thinking about contacting 3 on my side lol

Just thought I would post here: I have Aperture on a MacPro 2x2.66 Ghz Dual-Core Intel Xeon with 17G ram and running OS 10.7.2 -- I upgraded an Aperture library of images in 2011 to ver. 3.2 and it works fine but if I try to open any other library [others are 3.1.3] it asks to upgrade and I say yes then it goes on forever.

How do I bump back to 3.1.3 - I'm sure I can survive using that for a time but I don't know how to do that =

Welcome to Aperture 3.2. We Photographers, have been chasing our tails over this. "Upgrade", for 13 days now, and there has not been one official response from tech on a fix. There are some similar patterns of issues. There are variances from one case to the next as to the particular sympomatic occurances, but one thing is ovious, the Aperture 3.2 upgrade has corrupted Photo libraries, and its a shame. I have my experience with this. My first log was to revert back to 3.1.3. Yet Apple says they don't sell 3.1.3 anymore. They advised finding a Aperture 3.1.3 CD "SOMEWHERE"!! and reload. Another words reach down for another $199.00, thats your problem PAL. I'm getting really tired of this.

I was able to bump back the app to 3.1.3 because I had a backup - it was a click and drag operation and seems to be fine...I am now doing some cleaning up of permissions etc. before using the 'old' app to open the libraries and I guess we'll see what happens = just to be careful I copied the one library that was working fine in 3.2 and then will see what it takes to convert it back to 3.1.3 - that's my Q - the app isn't a problem, it's what to do about the new 3.2 library - but at least it'll be copied and if I have to I'll reimport = will report back

I have the same issue others are experiencing (EXC_BAD_INSTRUCTION, Thread 22 crashed with X86 Thread State (32-bit)), and wish Apple would have prevented the auto-upgrade, or at least warned me before 😟

I too have a MacBook1,1.

Thanks sjazbec. Do you know if there is a way to open a 3.2 updated library in 3.1. Otherwise (although hopefully Apple will fix the issue) I could only use the library initially on the core duo MBPS and then once opened on the (studios) Lion iMac it would be updated and not available to the MBP?

I will probably try to upgrade to Aperture 3.2 (currently 3.1.3), and I have two backups of my application as well as my libraries. My question is simple. What are the steps to revert back to 3.1.3 should 3.2 be a bad boy. What files from my backup system do I need to bring back and where do I put them. Are there 3.2 associated files that I should delete? Will this approach have a adverse effect on my ability to see future upgrades.

I am not an expert, but from this I have learnt that you should not yet upgrade if you have a core duo or earlier machine (so about five years). My MBP core duo crashed whenever I tried to touch a raw file. I was lucky as both the app and library were in time machine, so I just went back two days, replaced both and had no issues since. If you have a newer machine I would backup both before you grade. Think twice if you have a 5 year old machine before Apple decide to tell us that they are aware of the issue and roll out an update to the update!

Right the steps:

1) Backup Libraries ~/username/Pictures/Aperture-Library

2) Backup /Applications/Aperture

3) Backup ~/username/Library

4) Backup /Library/Application Support/Aperture

5) Update and test, test and test some more

6) If things go well no problems

7) If not delete the files backedup in steps 1 - 4 (off couse not the backups LOL :-)) )

8) Delete all /Library/Caches/com.apple.*

9) Delete ~/username/Library/Cashes/com.apple.Aperture

10) Delete ~/username/Library/Preferences/com.apple.Aperture.plist

11) I like to do a reboot at this point.

12) restore the files you backuped in step 1 - 4

hope this helps

step's 8 - 10 can help speed up Aperture 3.1 if it's getting slugish

Good stuff. Interestingly I only replaced app and library (in pictures) and all seems OK - was I lucky or should I replace the others (via time machine)?

I found the bit about deleteing the caches after googleing around for ways to speed up AP..

It appears that contra to what one may think deleteing the caches once evey 3 mounths or so can help keep AP.. working faster. It seems that perhaps the caches get out of sync/or something and the time tacken by the OS/AP getting them back in sync slows AP... down the opsite to what caches should do.

I am on a late 2007 Core 2 Duo iMac and aperture will not install the update. My 17" mpb took the update no problem and I typically share my libraries between the two constantnly. For now, I'm not using the mbp on active libraries for fear of the mess I read here.

2.8 / Core 2 Duo

4GB RAM

If I use SU to try and bring it down, it goes corrupt. If I download the 3.2 .dmg update from the support page- it will download the entire 667 MB and then the .dmg file errors an invalid checksum on extraction.

I was reading this thread and then dropped reading it because of monkey-type slams and mine-is-better bs.

Should I bother trying to figure out this mess or leave aperture well enough alone on the iMac (it soo kills me not to be able to update the application I love more than anything)?

sidenote- Am I really the only photog/one out there that would never consider using Time Machine specifically because of how it handles the aperture library? Did they fix the fact that Time Machine will re:copy an entire 100 GB library from bottom to top if I adjust or modify one file in the library?