Aperture 3.2 upgrade (from 3.1.3) crash continuously

those plugins might be incompatible. Happens all the time when the hosting app is updated.

You could try launching Aperture in 32bit mode, see if that helps , "get-info" on the app's icon and check "run in 32bit compatibility mode".

You could also trash the preferences and reset Aperture to factory values : /USER/Library/preferences - look for com.apple.aperture.plist, that holds the settings for the app that might have been borked,

I updated from 3.1.3 to 3.2 in OSX 10.7.2 and all is working. ( I don't have plugins, only presets from 3rd parties ) So your experience is not the default.

I am having the same problem after the Aperture 3.2 upgrade, ... and am using OS 10.6.8.

However, the crashes seem to occur only when I try to access RAW images and projects. JPEG images and projects open without issue.

I have the same issue. Only crashes when opening RAW files. I'm running 10.6.8. Come on Apple get this sorted asap! I need Aperture for my work!

I get the same problem. But i found the cause, and I did send a bug report. Unfortunately, you are (as me) out of luck.

It appears Aperture 3.2 is using SSE3 extensions, specifly aperture crashes when trying to use the 'palignr' instruction. Those of us with Intel core duo processors do not have SSE3, and the application will crash if it uses any instructions that the CPU does not recognize. (Illegal/Bad instruction)

The only chance we have is

A) Downgrade, both application and any updated Library.

B) make Apple support Intel Core Duo again. I believe it should be quite easy. Just set the correct build flags, and do a new release. I doubt any code changes are the cause of this. Lets hope 🙂

I do have a few plugins, theoreticly it be might be because of them. But a quick test would be to simply remove them. I doubt it would change anything.

I'm running on a Intel Core 2 duo Macbook and have not had any problems. It is a Macbook 5.1

Where speificaly did you come up with this diagnoses?

In addition I'm running Aperture in 64bit mode. works fine.

Great post frej! Thats just what I thought the issue was 😉. How can you downgrade the Library? I am desperate to get this working as have clients waiting for jobs.

I'm running on a Intel Core 2 duo Macbook and have not had any problems. It is a Macbook 5.1

Yes and then you have SSE3. Blame intel marketing. Intel Core Duo is _not_ the same as Intel Core 2 Duo. I have an old Macbook pro 1,1

Where speificaly did you come up with this diagnoses?

Well you asked.

1) First started aperture at commandline. It only gave me 'Illegal Instruction'. But it was a hint.

2) Run aperture in a debugger (i used gdb). It freezes the program when crashing allowing me to inspect quite a bit.

I got this:

Program received signal EXC_BAD_INSTRUCTION, Illegal instruction/operand.

[Switching to process 2987 thread 0xcc03]

0x0162b399 in DGConvertFromRGB16ToRGBA16 ()

3)So now we have a function and code address.

But gdb can print the actual instructions, by simply reading the binary code.

So:

'disassemble DGConvertFromRGB16ToRGBA16'

prints a page full of instructions, and we need to know which caused the problem, we have the address but an offset number is easier for humans (at least me) than hex addresses.

4)

'info registers'

gives us among others:

eip 0x162b399 0x162b399 <DGConvertFromRGB16ToRGBA16+161>

Using the offset address from data in 3)

0x0162b399 <DGConvertFromRGB16ToRGBA16+161>: palignr $0x8,%xmm2,%xmm4

And the offending instruction is palignr. Quick googling show that it is part of SSE3.

Note that the hex adress matches as well, so if i was really clever i had just used that 😟, they are ordered as well 🙂

Sometimes a Msc in comp.sci helps 😉

Just did my first imports from a Canon 40d RAW images into 3.2 and still no problems. This is on an iMac again Core 2 duo.

So I'm not saying you folks aren't having problems but it isn't as simple as being on a core 2 duo system or importing RAW files.

You should go back to the priestine state and before adding back in the plugins do the import that's causing the crash, see if that changes anything.

Apple iMac Intel Core Duo is 32 bit - so I think you might be lucky if the issue does eventually revolves around CPU / Xcode compiler specs.

The application is a universal binary here and runs finely on a 32bit cpu until it crashes a few seconds in. A 64bit application would crash _immediately_ on a 32bit cpu.

My apologies I saw the core duo and my mind added the 2.

I hope Apple don't take ages getting a fix out. I can see people on older systems being a low priority. Come on Apple!

Great post frej! Thats just what I thought the issue was 😉. How can you downgrade the Library? I am desperate to get this working as have clients waiting for jobs.

I have no clue about how to downgrade library. It's likely possible by comparing the database schema they use (aperture uses sqlite), and write a custom conversion script. But it's also quite a bit of work, depending on the amount of changes they actually made. They might have changed parts outside the sqlite database as well.

You best bet is getting both Library and Application from a backup.

I can run aperture a bit longer holding shift key on during aperture launch. I found something on google that it would stop aperture from any image processin, like thumbnails. But viewing any RAW causes a crash for me again. The same.