my iphoto has what seems to become corrupt twice in the last 2 months. It just happened for the second time, and I hate having to rebuild it.
Any suggestions as to how to prevent this from happening again?
Is this common with iphoto 11 and OS 10.7.2?
iMovie '11, Mac OS X (10.7.2)
Depends on that the corruption is. Often if there's an interruption of some sort while iPhoto is writing to its databae file the library can be damaged. Also important is how much free space you have on the boot drive.
OT
it happens when i try to start iphoto, it then crashes unexpectantly. i currently have 421.35GB free on my boot drive.
Below is the first part of the error.
| Process: | iPhoto [2917] |
| Path: | /Applications/iPhoto.app/Contents/MacOS/iPhoto |
| Identifier: | com.apple.iPhoto |
| Version: | 9.2.1 (9.2.1) |
| Build Info: | iPhotoProject-628000000000000~3 |
| Code Type: | X86 (Native) |
Parent Process: launchd [131]
| Date/Time: | 2012-01-31 17:08:45.180 -0500 |
| OS Version: | Mac OS X 10.7.2 (11C74) |
Report Version: 9
| Interval Since Last Report: | 296209 sec |
| Crashes Since Last Report: | 14 |
Per-App Interval Since Last Report: 23915 sec
Per-App Crashes Since Last Report: 10
| Anonymous UUID: | 7EAACBC0-BEDC-4AF7-87DA-B3F2264E1097 |
Crashed Thread: 32
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: 0x000000000000000a, 0x0000000016050000
VM Regions Near 0x16050000:
| MALLOC_SMALL | 0000000014000000-0000000016000000 [ 32.0M] rw-/rwx SM=PRV |
| --> mapped file | 0000000016000000-00000000162bb000 [ 2796K] r--/rwx SM=COW /Users/USER/Pictures/*/*.JPG |
| MALLOC_TINY | 0000000016300000-0000000016400000 [ 1024K] rw-/rwx SM=COW |
Application Specific Information:
objc[2917]: garbage collection is OFF
Thread 0:: Dispatch queue: com.apple.main-thread
| 0 libsystem_kernel.dylib | 0x9bd6bcfa __pwrite + 10 |
| 1 com.apple.iLifeSQLAccess | 0x0184bec7 unixWrite + 87 |
| 2 com.apple.iLifeSQLAccess | 0x0184bbc7 writeJournalHdr + 471 |
| 3 com.apple.iLifeSQLAccess | 0x0184b80e pager_open_journal + 302 |
| 4 com.apple.iLifeSQLAccess | 0x0184b6c2 sqlite3PagerBegin + 162 |
| 5 com.apple.iLifeSQLAccess | 0x018354e1 sqlite3BtreeBeginTrans + 2273 |
| 6 com.apple.iLifeSQLAccess | 0x0182f653 sqlite3VdbeExec + 31907 |
| 7 com.apple.iLifeSQLAccess | 0x0182762c sqlite3_step + 2812 |
| 8 com.apple.iLifeSQLAccess | 0x0181468b sqlite3_exec + 523 |
| 9 com.apple.iLifeSQLAccess | 0x018a78f5 -[HgKDatabaseManager openAsReadOnly:attemptJournalCleanup:] + 549 |
| 10 com.apple.iLifeSQLAccess | 0x0180cb91 -[HgKDatabaseManager openAsReadOnly:] + 49 |
| 11 com.apple.iLifePageLayout | 0x01432f91 -[KHUserProjectDatabase openDatabaseWithOptions:] + 577 |
| 12 com.apple.iLifePageLayout | 0x0132c5d7 -[KHController attemptDBLoad] + 487 |
| 13 com.apple.iLifePageLayout | 0x013257c0 -[KHController setDelegate:] + 80 |
| 14 com.apple.iPhoto | 0x00033a80 0x1000 + 207488 |
| 15 com.apple.Foundation | 0x97883f49 __-[NSNotificationCenter addObserver:selector:name:object:]_block_invoke_1 + 49 |
| 16 com.apple.CoreFoundation | 0x91c09ff3 ___CFXNotificationPost_block_invoke_1 + 275 |
| 17 com.apple.CoreFoundation | 0x91bd4d78 _CFXNotificationPost + 2776 |
| 18 com.apple.Foundation | 0x9786f136 -[NSNotificationCenter postNotificationName:object:userInfo:] + 92 |
| 19 com.apple.AppKit | 0x999bad05 -[NSApplication _postDidFinishNotification] + 259 |
| 20 com.apple.AppKit | 0x999ba9f8 -[NSApplication _sendFinishLaunchingNotification] + 84 |
| 21 com.apple.AppKit | 0x999b9518 -[NSApplication(NSAppleEventHandling) _handleAEOpenEvent:] + 277 |
| 22 com.apple.AppKit | 0x999b922e -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 377 |
| 23 com.apple.CoreFoundation | 0x91c22548 -[NSObject performSelector:withObject:withObject:] + 72 |
| 24 com.apple.Foundation | 0x978a921a __-[NSAppleEventManager setEventHandler:andSelector:forEventClass:andEventID:]_block_invoke_1 + 121 |
| 25 com.apple.Foundation | 0x978a7fcd -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 476 |
| 26 com.apple.Foundation | 0x978a7da1 _NSAppleEventManagerGenericHandler + 234 |
| 27 com.apple.AE | 0x9c7d8045 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned long, unsigned char*) + 202 |
| 28 com.apple.AE | 0x9c7c1b67 _ZL25dispatchEventAndSendReplyPK6AEDescPS_ + 43 |
| 29 com.apple.AE | 0x9c7c1a54 aeProcessAppleEvent + 253 |
| 30 com.apple.HIToolbox | 0x96299fea AEProcessAppleEvent + 103 |
| 31 com.apple.AppKit | 0x999b62af _DPSNextEvent + 1301 |
| 32 com.apple.AppKit | 0x999b58ab -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 113 |
| 33 com.apple.AppKit | 0x999b1c22 -[NSApplication run] + 911 |
| 34 com.apple.AppKit | 0x99c4618a NSApplicationMain + 1054 |
| 35 com.apple.iPhoto | 0x0001159a 0x1000 + 66970 |
| 36 com.apple.iPhoto | 0x00010a29 0x1000 + 64041 |
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
| 0 libsystem_kernel.dylib | 0x9bd6b90a kevent + 10 |
| 1 libdispatch.dylib | 0x91ac2c58 _dispatch_mgr_invoke + 969 |
| 2 libdispatch.dylib | 0x91ac16a7 _dispatch_mgr_thread + 53 |
Thread 2:
| 0 libsystem_kernel.dylib | 0x9bd6a83e __psynch_cvwait + 10 |
| 1 libsystem_c.dylib | 0x97c7fe78 _pthread_cond_wait + 914 |
| 2 libsystem_c.dylib | 0x97c7ff7b pthread_cond_timedwait_relative_np + 47 |
| 3 com.apple.Foundation | 0x978fe507 -[NSCondition waitUntilDate:] + 427 |
| 4 com.apple.Foundation | 0x978c492a -[NSConditionLock lockWhenCondition:beforeDate:] + 294 |
| 5 com.apple.Foundation | 0x978c47fe -[NSConditionLock lockWhenCondition:] + 69 |
| 6 com.apple.proxtcore | 0x0175c702 -[XTMsgQueue waitForMessage] + 50 |
| 7 com.apple.proxtcore | 0x0175b6b0 -[XTThread run:] + 416 |
| 8 com.apple.Foundation | 0x978cbf7d -[NSThread main] + 45 |
| 9 com.apple.Foundation | 0x978cbf2d __NSThread__main__ + 1582 |
| 10 libsystem_c.dylib | 0x97c7bed9 _pthread_start + 335 |
| 11 libsystem_c.dylib | 0x97c7f6de thread_start + 34 |
Often EXC_BAD_ACCESS (SIGBUS) is associated with bad memory. Check to make sure the memory chips are securely mounted.
Was the rebuilding successful each time and how full a rebuild did you have to do? I would consider getting an external FW hard drive and use it with Time Machine to keep current backups of your library and any other important files.
This is a long shot but the OS X Lion Update 10.7.3 (Client Combo) updater was released today. If it's not memory then install the update and 😟 hope for the best. Don't use Software Update to apply the update. Use the link I gave.
I could suggest you create a new test library to see if the problem persists with it but it might take you too long using it to find out since it's somewhat infrequent.
IPhoto Becoming corrupt.
