Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

New to Aperture, Longtime iPhoto User - Aperture Crashing!

Hello Aperture Community!


I recently purchased Aperture after having lots of problems with my iPhoto library crashing - issues which were not resolved by rebuilding the library within iPhoto and by attempts to us iPhoto Library Manager to do a complete rebuild. I have a lot of experience with iPhoto and have much appreciated the guidance I have had from the iPhoto community (and I have tried to help others as well).


I moved to Aperture in the hopes that migrating my images would solve the problem. I have a large library >90K pictures and it took about a day to import to Aperture via File>Import>Library command. The resulting file is over 600 GB I was dismayed that it automatically randomizes my Event order and creates Projects for every album and event - but I suspect that is normal. My Album order was likewise randomized - everything now in alphabetical order rather than the custom order I had used in iPhoto. Oh well, another few hours work should solve that.


Then, Aperture crashed as well. I visited http://www.nooooooooooooooo.com a couple times and felt better. Crash report through crashed thread is below. Any ideas would be much appreciated - I am assuming that I have a corrupt file which is crashing it, possibly as Faces makes its way through the library. Is that a good assumption? Any way to find the file? Anyone out there who has faced similar issues just to commiserate with?


Thanks for any help!


Bob


Process: Aperture [5705]

Path: /Applications/Aperture.app/Contents/MacOS/Aperture

Identifier: com.apple.Aperture

Version: 3.4.3 (3.4.3)

Build Info: Aperture-310022000000000~2

App Item ID: 408981426

App External ID: 12009533

Code Type: X86-64 (Native)

Parent Process: launchd [141]

User ID: 501



Date/Time: 2012-11-30 20:54:08.751 -0500

OS Version: Mac OS X 10.8.2 (12C60)

Report Version: 10



Crashed Thread: 7



Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x00007fc727700000



VM Regions Near 0x7fc727700000:

MALLOC_TINY 00007fc727000000-00007fc727700000 [ 7168K] rw-/rwx SM=PRV

-->

MALLOC_SMALL 00007fc727800000-00007fc728000000 [ 8192K] rw-/rwx SM=PRV



Thread 0:: Dispatch queue: com.apple.main-thread

0 libsystem_kernel.dylib 0x00007fff916b4686 mach_msg_trap + 10

1 libsystem_kernel.dylib 0x00007fff916b3c42 mach_msg + 70

2 com.apple.CoreFoundation 0x00007fff8f7bc803 __CFRunLoopServiceMachPort + 195

3 com.apple.CoreFoundation 0x00007fff8f7c1ee6 __CFRunLoopRun + 1078

4 com.apple.CoreFoundation 0x00007fff8f7c16b2 CFRunLoopRunSpecific + 290

5 com.apple.HIToolbox 0x00007fff8d56d0a4 RunCurrentEventLoopInMode + 209

6 com.apple.HIToolbox 0x00007fff8d56ce42 ReceiveNextEventCommon + 356

7 com.apple.HIToolbox 0x00007fff8d56ccd3 BlockUntilNextEventMatchingListInMode + 62

8 com.apple.AppKit 0x00007fff8bd64613 _DPSNextEvent + 685

9 com.apple.AppKit 0x00007fff8bd63ed2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128

10 com.apple.Aperture 0x00000001010eb205 0x100c75000 + 4678149

11 com.apple.AppKit 0x00007fff8bd5b283 -[NSApplication run] + 517

12 com.apple.prokit 0x000000010219c324 NSProApplicationMain + 378

13 com.apple.Aperture 0x0000000100c854a2 0x100c75000 + 66722

14 com.apple.Aperture 0x0000000100c84df4 0x100c75000 + 65012



Thread 1:: Dispatch queue: com.apple.libdispatch-manager

0 libsystem_kernel.dylib 0x00007fff916b6d16 kevent + 10

1 libdispatch.dylib 0x00007fff8d368dea _dispatch_mgr_invoke + 883

2 libdispatch.dylib 0x00007fff8d3689ee _dispatch_mgr_thread + 54



Thread 2:

0 libsystem_kernel.dylib 0x00007fff916b60fa __psynch_cvwait + 10

1 libsystem_c.dylib 0x00007fff88c34fc3 _pthread_cond_wait + 927

2 com.apple.Foundation 0x00007fff9098d933 -[NSCondition waitUntilDate:] + 357

3 com.apple.Foundation 0x00007fff9098d789 -[NSConditionLock lockWhenCondition:beforeDate:] + 235

4 com.apple.proxtcore 0x0000000102e6f03a -[XTMsgQueue waitForMessage] + 47

5 com.apple.proxtcore 0x0000000102e6e282 -[XTThread run:] + 329

6 com.apple.Foundation 0x00007fff90962612 __NSThread__main__ + 1345

7 libsystem_c.dylib 0x00007fff88c30742 _pthread_start + 327

8 libsystem_c.dylib 0x00007fff88c1d181 thread_start + 13



Thread 3:

0 libsystem_kernel.dylib 0x00007fff916b60fa __psynch_cvwait + 10

1 libsystem_c.dylib 0x00007fff88c34fc3 _pthread_cond_wait + 927

2 com.apple.Foundation 0x00007fff9098d933 -[NSCondition waitUntilDate:] + 357

3 com.apple.Foundation 0x00007fff9098d789 -[NSConditionLock lockWhenCondition:beforeDate:] + 235

4 com.apple.proxtcore 0x0000000102e6f03a -[XTMsgQueue waitForMessage] + 47

5 com.apple.proxtcore 0x0000000102e6e282 -[XTThread run:] + 329

6 com.apple.Foundation 0x00007fff90962612 __NSThread__main__ + 1345

7 libsystem_c.dylib 0x00007fff88c30742 _pthread_start + 327

8 libsystem_c.dylib 0x00007fff88c1d181 thread_start + 13



Thread 4:

0 libsystem_kernel.dylib 0x00007fff916b60fa __psynch_cvwait + 10

1 libsystem_c.dylib 0x00007fff88c34fc3 _pthread_cond_wait + 927

2 com.apple.Foundation 0x00007fff9098d933 -[NSCondition waitUntilDate:] + 357

3 com.apple.Foundation 0x00007fff9098d789 -[NSConditionLock lockWhenCondition:beforeDate:] + 235

4 com.apple.proxtcore 0x0000000102e6f03a -[XTMsgQueue waitForMessage] + 47

5 com.apple.proxtcore 0x0000000102e6e282 -[XTThread run:] + 329

6 com.apple.Foundation 0x00007fff90962612 __NSThread__main__ + 1345

7 libsystem_c.dylib 0x00007fff88c30742 _pthread_start + 327

8 libsystem_c.dylib 0x00007fff88c1d181 thread_start + 13



Thread 5:

0 libsystem_kernel.dylib 0x00007fff916b60fa __psynch_cvwait + 10

1 libsystem_c.dylib 0x00007fff88c34fc3 _pthread_cond_wait + 927

2 com.apple.Foundation 0x00007fff9098d933 -[NSCondition waitUntilDate:] + 357

3 com.apple.Foundation 0x00007fff9098d789 -[NSConditionLock lockWhenCondition:beforeDate:] + 235

4 com.apple.proxtcore 0x0000000102e6f03a -[XTMsgQueue waitForMessage] + 47

5 com.apple.proxtcore 0x0000000102e6e282 -[XTThread run:] + 329

6 com.apple.Foundation 0x00007fff90962612 __NSThread__main__ + 1345

7 libsystem_c.dylib 0x00007fff88c30742 _pthread_start + 327

8 libsystem_c.dylib 0x00007fff88c1d181 thread_start + 13



Thread 6:

0 libsystem_kernel.dylib 0x00007fff916b6faa pread + 10

1 com.apple.ImageIO.framework 0x00007fff9269d244 CGImageReadGetBytesAtOffset + 569

2 com.apple.ImageIO.framework 0x00007fff9269beed _CGImageSourceBindToPlugin + 289

3 com.apple.ImageIO.framework 0x00007fff9269d496 _CGImageSourceGetPropertiesAtIndexInternal + 35

4 com.apple.ImageIO.framework 0x00007fff9269d43f CGImageSourceCopyPropertiesAtIndex + 139

5 com.apple.RedRock 0x00000001016c4c2b -[RKMetadata initWithPath:cgImageSource:imageIOMethodVersion:includeFileAttributes:includeRa w:sidecarFile:movie:] + 1062

6 com.apple.RedRock 0x00000001016c47ff -[RKMetadata initWithPath:imageIOMethodVersion:includeRaw:sidecarFile:] + 53

7 com.apple.RedRock 0x00000001016c4690 -[RKMetadata initWithPath:imageIOMethodVersion:includeRaw:filetype:] + 107

8 com.apple.RedRock 0x00000001016c3c87 -[RKVersion(RawSupport) cgImagePropertiesWithRaw:] + 443

9 com.apple.RedRock 0x00000001018c98be -[RKVersion(Imaging) masterSizeForMaster:] + 161

10 com.apple.RedRock 0x00000001018a30eb -[RKMasterImageRequest initWithVersion:master:size:] + 212

11 com.apple.RedRock 0x000000010186554a -[RKVersion(Geode) newMasterImageRequestForMaster:size:useOriginal:description:] + 161

12 com.apple.RedRock 0x000000010186549a -[RKVersion(Geode) newMasterImageRequestForMaster:size:useOriginal:] + 82

13 com.apple.RedRock 0x0000000101878e2a -[RKImageCache imageForVersion:ofSize:format:colorSpace:description:flags:readyHandler:] + 613

14 com.apple.RedRock 0x00000001018b5dca -[FaceTileFactory cache:cacheStore:onFulfillRequest:intoPageRef:] + 1162

15 com.apple.RedRock 0x00000001019c9e36 -[FaceTiler renderFaceTileForRequestHandler:] + 326

16 com.apple.proxtcore 0x0000000102e6fa85 -[XTDistributor distributeMessage:] + 299

17 com.apple.proxtcore 0x0000000102e6f4d9 -[XTThread handleMessage:] + 342

18 com.apple.proxtcore 0x0000000102e6e292 -[XTThread run:] + 345

19 com.apple.Foundation 0x00007fff90962612 __NSThread__main__ + 1345

20 libsystem_c.dylib 0x00007fff88c30742 _pthread_start + 327

21 libsystem_c.dylib 0x00007fff88c1d181 thread_start + 13



Thread 7 Crashed:

0 libsystem_c.dylib 0x00007fff88c1da50 memmove$VARIANT$sse42 + 136

1 com.apple.geode 0x0000000102c6b68a -[DGJPEGDecodeRequest initWithJPEGDataRef:subSampleFactor:] + 316

2 com.apple.geode 0x0000000102bbf355 -[DGImageJPEGCachePage decodedJPEGImageWithFormat:] + 457

3 com.apple.geode 0x0000000102bbcba9 -[DGImageCachePage copyPage:fromRect:toRect:] + 746

4 com.apple.geode 0x0000000102c37348 -[DGTier2Factory readRequest:intoPageRef:] + 858

5 com.apple.geode 0x0000000102c37814 -[DGTier2Factory cache:cacheStore:onFulfillRequest:intoPageRef:] + 589

6 com.apple.proxtcore 0x0000000102e8f25a -[XTCacheFactory backgroundFulfillment:] + 532

7 com.apple.proxtcore 0x0000000102e6fb16 -[XTDistributor distributeMessage:] + 444

8 com.apple.proxtcore 0x0000000102e6f4d9 -[XTThread handleMessage:] + 342

9 com.apple.proxtcore 0x0000000102e6e292 -[XTThread run:] + 345

10 com.apple.Foundation 0x00007fff90962612 __NSThread__main__ + 1345

11 libsystem_c.dylib 0x00007fff88c30742 _pthread_start + 327

12 libsystem_c.dylib 0x00007fff88c1d181 thread_start + 13

iMac (27-inch Mid 2011), OS X Mountain Lion (10.8.2)

Posted on Dec 1, 2012 5:42 AM

Reply
Question marked as Best reply

Posted on Dec 1, 2012 6:27 AM

Bob,

When does the crash happen? Directly on start up, or when you start working with the library?


The bad access error really looks like a data error - it crashes when accessing a jpeg.


It looks like you imported this problem from iPhoto. Do you remember which iPhoto events you had imported to iPhoto, right before the problem started?


To check, if a corrupted image is causing the crashes, I'd recommend two things:

  1. Launch Aperture with the ⌥-key held down to create a new library and import some test images. Can you work with this library without problems?
  2. If Aperture is o.k. with a new library, launch it again on your main library: Select the library in the Finder and hold the "Shift" key down, while you double click the library. This will defer the generation of previews. If indeed a corrupted image is causing the crashes, Aperture usually will crash when trying to render a preview for the image. Deferring this should enable you to browse your library and check the projects you most recently imported.


Post back, if you can launch Aperture with preview generation turned off, then we can try to advise you how to find a corrupted image.


One more thing; if you could not repair your library while still using iPhoto, you might consider to try to repair the library and the permissions now in Aperture.

See: Aperture 3 User Manual: Repairing and Rebuilding Your Aperture Library


Regards

Léonie

4 replies
Question marked as Best reply

Dec 1, 2012 6:27 AM in response to Robert Stone

Bob,

When does the crash happen? Directly on start up, or when you start working with the library?


The bad access error really looks like a data error - it crashes when accessing a jpeg.


It looks like you imported this problem from iPhoto. Do you remember which iPhoto events you had imported to iPhoto, right before the problem started?


To check, if a corrupted image is causing the crashes, I'd recommend two things:

  1. Launch Aperture with the ⌥-key held down to create a new library and import some test images. Can you work with this library without problems?
  2. If Aperture is o.k. with a new library, launch it again on your main library: Select the library in the Finder and hold the "Shift" key down, while you double click the library. This will defer the generation of previews. If indeed a corrupted image is causing the crashes, Aperture usually will crash when trying to render a preview for the image. Deferring this should enable you to browse your library and check the projects you most recently imported.


Post back, if you can launch Aperture with preview generation turned off, then we can try to advise you how to find a corrupted image.


One more thing; if you could not repair your library while still using iPhoto, you might consider to try to repair the library and the permissions now in Aperture.

See: Aperture 3 User Manual: Repairing and Rebuilding Your Aperture Library


Regards

Léonie

Dec 1, 2012 8:26 PM in response to léonie

Léonie,


Thanks for your advice. Oddly, I am able to work for extended periods with even the library that crashed even if previews are being rendered in background. That is the frustrating thing in that it is an intermittent failure. But, I think I may be onto something. I found an image which is cleary corrupt - though that does not mean it has to be the cause, of course. I found that file (which was fairly recently imported) in Aperture and when manipulating it got the beach ball for about a minute but the program did not totally crash. I tried importing just a small set of pictures including that file to a new iPhoto library and noticed something - the thumbnail does not match the full sized image, even after doing a thumbnail rebuild. Here are the images:User uploaded file

There is a stripe in the center which seems to shift after opening as well. Clearly it is corrupt - is there any way to know for sure this is the culprit?


Bob

Dec 7, 2012 5:56 PM in response to léonie

I am now certain that the file mentioned above / corrupt jpeg is the source of my problems. I was transferring data from one hard drive to another - about 1 TB of data - and the transfer stopped after many hours noting that the finder was unable to transfer this one file among many many thousands. I tried to throw the file in the trash and hung the finder that way as well. I figure that if this file can crash the whole computer then crashing iPhoto or Aperture would be small potatoes in comparison.


Thanks to leonieDF for your help!


I hope this post helps someone at some point.

New to Aperture, Longtime iPhoto User - Aperture Crashing!

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.