Skip navigation

AP crashing while building thumbnails

558 Views 12 Replies Latest reply: Apr 13, 2013 1:53 PM by dbmoore RSS
dbmoore Level 1 Level 1 (95 points)
Currently Being Moderated
Mar 13, 2013 5:56 PM

Ap 3.4.3 has been constantly crashing.  Ive done Repair Rebuild lib, reinstalled ap,  from CD Ap3,   reiinstalled 10.8.2 .  After all that it wants to rebuild previews so Im letting it run but it crashes while building preview.  Lib is Referenced with images on Drobo S.  Main HD is an ssd in the MBP while the lib is on the other internal HD formatted for osx journaled. Disk utilitys says internal 500g disk is ok.  I have repaired and reubuild the library many many times.  Any suggestions??????

 

Process:         Aperture [371]

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

Identifier:      com.apple.Aperture

Version:         3.4.3 (3.4.3)

Build Info:      Aperture-310022000000000~1

Code Type:       X86-64 (Native)

Parent Process:  launchd [152]

User ID:         501

 

Date/Time:       2013-03-13 17:37:34.074 -0700

OS Version:      Mac OS X 10.8.2 (12C60)

Report Version:  10

 

Interval Since Last Report:          219506 sec

Per-App Interval Since Last Report:  110199 sec

Anonymous UUID:                      C71C4B30-7E65-B442-AAC8-B87788846A44

 

Crashed Thread:  18  Dispatch queue: com.apple.photoapps.version

 

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: EXC_I386_GPFLT

 

Application Specific Information:

objc_msgSend() selector name: retain

 

 

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

0   libsystem_kernel.dylib                  0x00007fff86e7e686 mach_msg_trap + 10

1   libsystem_kernel.dylib                  0x00007fff86e7dc42 mach_msg + 70

2   com.apple.CoreFoundation                0x00007fff8e027803 __CFRunLoopServiceMachPort + 195

3   com.apple.CoreFoundation                0x00007fff8e02cee6 __CFRunLoopRun + 1078

4   com.apple.CoreFoundation                0x00007fff8e02c6b2 CFRunLoopRunSpecific + 290

5   com.apple.HIToolbox                     0x00007fff83f030a4 RunCurrentEventLoopInMode + 209

6   com.apple.HIToolbox                     0x00007fff83f02e42 ReceiveNextEventCommon + 356

7   com.apple.HIToolbox                     0x00007fff83f02cd3 BlockUntilNextEventMatchingListInMode + 62

8   com.apple.AppKit                        0x00007fff8237a613 _DPSNextEvent + 685

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

10  com.apple.Aperture                      0x00000001101d2205 0x10fd5c000 + 4678149

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

12  com.apple.prokit                        0x0000000111282324 NSProApplicationMain + 378

13  com.apple.Aperture                      0x000000010fd6c4a2 0x10fd5c000 + 66722

14  com.apple.Aperture                      0x000000010fd6bdf4 0x10fd5c000 + 65012

 

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

0   libsystem_kernel.dylib                  0x00007fff86e80d16 kevent + 10

1   libdispatch.dylib                       0x00007fff83ccbdea _dispatch_mgr_invoke + 883

2   libdispatch.dylib                       0x00007fff83ccb9ee _dispatch_mgr_thread + 54

 

Thread 2:

0   libsystem_kernel.dylib                  0x00007fff86e7e6c2 semaphore_wait_trap + 10

1   libdispatch.dylib                       0x00007fff83ccdc32 _dispatch_thread_semaphore_wait + 16

2   libdispatch.dylib                       0x00007fff83cce424 _dispatch_sync_f_slow + 140

3   com.apple.RedRock                       0x00000001107807e5 -[RKVersion(Imaging) imageProxyState] + 150

4   com.apple.RedRock                       0x000000011096dde1 -[RKImageCache renderThumbnailForVersionAddress:force:workOrder:] + 778

5   com.apple.RedRock                       0x000000011096e972 -[RKImageCache renderThumbnailsForVersionAddressHandler:] + 154

6   com.apple.proxtcore                     0x0000000111f58f7c -[XTList makeObjectsPerformSelector:withObject:] + 59

7   com.apple.proxtcore                     0x0000000111f58b3a -[XTDistributor distributeMessage:] + 480

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

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

10  com.apple.Foundation                    0x00007fff8af57612 __NSThread__main__ + 1345

11  libsystem_c.dylib                       0x00007fff8ae09742 _pthread_start + 327

12  libsystem_c.dylib                       0x00007fff8adf6181 thread_start + 13

Aperture 3, OS X Mountain Lion (10.8.2), AP 3.4.3 2009MBP 8GB ram int ssd
  • Frank Caggiano Level 7 Level 7 (22,815 points)
    Currently Being Moderated
    Mar 13, 2013 6:30 PM (in response to dbmoore)

    Open Aperture while holding down the shift key. This will force Aperture to skip preview generation. If Aperture runs it means you have a corrupted image in the library.

     

    Post back the results and we'll take if from there,

  • Frank Caggiano Level 7 Level 7 (22,815 points)
    Currently Being Moderated
    Mar 13, 2013 8:55 PM (in response to dbmoore)

    So did Aperture start and run ok when started with the shift key held?

  • léonie Level 8 Level 8 (46,485 points)
    Currently Being Moderated
    Mar 14, 2013 1:15 AM (in response to dbmoore)

    Lib is Referenced with images on Drobo S. 

    How is your "Drobo S. " formatted? Preview generation can also fail, if the filename has a corruption, not only if the media part of an image has corrupted data. If your Drobo is not MacOS Extended you may have copied a filename that MacOS X cannot deal with, or one of your image filenames may contain invisible characters. So, in addition to Frank's advice, I'd suggest also to screen the filenames, not only "Probably something with a mask in channels from PS". And frequently it is a video that was imported together with the image files, that is causing the preview generation to crash.

     

    One way to search would be to turn on the Activity Window (Window > Show Activity) and to select your most recent imports in the Browser, then use the command "Photos > Update Previews". The Activity window will show you the filename of the currently processed image. Look, if Aperture is unusally slow on some images.

    • If it crashes, you will know that the culprit is among the currently processed set.
    • Then use Frank's "Divide and Conquer" strategy - I do not find a link to his post, where he described the method first. But the general idea is to split the set of the suspect images into halves:
      • Try to build previews for half of the suspect images. If it succedes, you'll know these images are o.k. If it does not succeed, even better. The culprit is within the batch you just processed.
      • Split the set again, and keep subdividing the part that makes Aperture crash.
      • By systematically splitting and testing partial sets of images you can test 1000000 images by only splitting the set of images to be tested twenty times. So it is not really hopeless, it only requires keeping track of images already tested. Having two albums "Images to be tested" and "Images already tested and ok" may help. If the images is among your most recently media and you only have to test 500 images or so, you should be done with 9 splits and tests.

     

    Good luck.

    Léonie

  • Frank Caggiano Level 7 Level 7 (22,815 points)
    Currently Being Moderated
    Mar 14, 2013 6:14 AM (in response to dbmoore)

    Pretty much everything still holds.

     

    It appears you have a corruption (either in the file data or filename) in the library.

     

    Setting Previews to never in the Preferences only keeps Aperture from generating previews in new projects. It says nothing about what happens with projects already in existence.

     

    If that preferences was ever set to generate previews then the projects that were made at that time are still generating previews.

  • léonie Level 8 Level 8 (46,485 points)
    Currently Being Moderated
    Mar 14, 2013 8:58 AM (in response to dbmoore)
    I think it the extra channel built in PS is  what gives AP a problem and not the Path.  But If its Paths then I need to delete those as well I guess.  Thanks for your help really appreciate it.

     

    I would test that by importing a Photoshop image with paths into a new Aperture library, created just for testing. Use "File > Switch to lIbrary > Other/new" to create test library and import one single image. Then you will see, what Aperture can handle.

     

    Aperture should be able to import tiffs and psd files with layers and alpha channel, only it does not promise to be able to edit them and to create correct thumbnails or previews.

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.