Aperture recently began crashing repeatedly on me during it's initial “Processing” phase. I've deleted the library then copied over a known good Aperture Library from a few weeks ago and it does the same. All's well if I hold down shift when opening it as it won't process, but I need to get past this. Below is the beginning of crash report. Anyone have any ideas?
Process: Aperture [10696]
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Identifier: com.apple.Aperture
Version: 3.2.3 (3.2.3)
Build Info: Aperture-203040000000000~3
Code Type: X86-64 (Native)
Parent Process: launchd [109]
Date/Time: 2012-03-29 21:23:19.596 -0500
OS Version: Mac OS X 10.7.3 (11D50b)
Report Version: 9
Interval Since Last Report: 556599 sec
Crashes Since Last Report: 20
Per-App Interval Since Last Report: 13052 sec
Per-App Crashes Since Last Report: 5
Anonymous UUID: F8D8199F-98D3-47A4-8307-32843B5F25F4
Crashed Thread: 21
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: 0x000000000000000a, 0x000000012dff0000
VM Regions Near 0x12dff0000:
MALLOC_LARGE (reserved 000000012d0ca000-000000012df30000 [ 14.4M] rw-/rwx SM=NUL reserved VM address space (unallocated)
–> mapped file 000000012df30000-000000012e0fd000 [ 1844K] r–/rwx SM=COW /Users/USER/Library/Application Support/iLifeAssetManagement/*/*.JPG
MALLOC_LARGE 000000012e0fd000-000000012e89c000 [ 7804K] rw-/rwx SM=PRV
Clif,
Sounds like a corrupt image. When you say it’s in the “processing” phase, are you looking at the activity monitor (menu: Window > Show Activity) and does it give you any other info, i.e. what file it might be stuck on?
If so, then launch holding shift as you’ve done then eliminate that file.
If not, then have you tried repairing or rebuilding the database yet? FAQ
@PhotoJoseph
— Have you signed up for the mailing list?
I had a similar situation where Aperture would hang upon importing. After working with Apple support, the ultimate solution for me was to run Aperture in 32 bit mode as opposed to 64 bit mode (I see from the data that you are running x64). Not a glowingly positive alternative I guess but it for me it was the best route as I think my only other option was to reformat/reinstall my MacOS and programs..
Hope this helps! Let us know..anyone know what I am missing/giving up by running in 32 bit? I’m not that much of a propeller head :-)
You are not giving up any features. Everything works the same as in 64-bit mode.
You could experience slower response in in 32-bit mode. However, if you are on a slow machine anyway, you will not notice any difference in speed.
After working with Apple and then digging more on my own the culprit was a failing hard drive. I replaced it and restored from Time Machine.
Ah, interesting. And all better now?
-Joseph
@PhotoJoseph
— Have you signed up for the mailing list?