Aperture Special Report: Frequent crashes -- try deleting .plist file; disconnecting devices; check for bad RAM

If you are experiencing repeated crashes with Aperture, the cause is likely one of the following: a corrupt image in your photo library or a corrupt .plist file.

Although locating a corrupt image can be difficult, deleting a corrupt .plist file is relatively straightforward, and involves dragging the following file to the trash while Aperture is closed:

• ~/Library/Preferences/com.apple.Aperture.plist

then launching the application again.

Bad RAM, errant USB devices can cause crashes If you are having problems with Aperture repeatedly crashing after a few minutes of operation, try disconnecting third-party USB devices (in some cases including keyboards and mice) and check for persistence of the problem.

You may also want to check for problematic RAM.

Index:

• Release Notes
• Aperture 1.0.1 persistently appearing in Software Update -- fix
• Aperture 1.0.1: Release notes; What is fixed, and not fixed
• Solution for importing metadata from iView MediaPro
• Artifacts when adjusting images with "auto levels"
• Burning CDs of photos from Aperture
• Dual monitor issues
• Cannot recognize some DNG files
• Duplicate image imports -- fix
• Frequent crashes -- try deleting .plist file; disconnecting devices; check for bad RAM
• Viewing the supported camera list
• Vault Issues: Corruption; Incorrect "not enough space" errors
• IPTC/ metadata issues
• Methods for doing RAW conversion in ACR
• Long progress indicator for 6x4 images
• Navigation pane erratically shifting
• No extra-.Mac Web publishing
• Performance issues with libraries imported from
• Problems with print ordering
• Problems with Slideshow during photo print ordering
• Sharing libraries between multiple users

Resources