Aperture 2.1.4 Hangs On Building Thumbnails

I have Aperture 2.1.4 and everytime I open a specific project (the one with the most images...800+) it hangs building thumbnails. I've tried the "check library consistency" but during Running VACUUM On Database it never gets past the 80% area on the progress bar. I let it go for at least 4 hours but that's as far as it goes. Any thoughts?

I would work my way through the steps listed on the Aperture 2: Troubleshooting Basics page;
http://support.apple.com/kb/HT2945
Not necessarily in that order though,
Delete Preferences,
Disk Utility, repair Permissions & Repair Disk
Consistency Check
Re-build LIbrary
Depending on the size of your library you need to expect that it may well take a lot longer than you have allowed, typically leave it to work until complete, it may well sit at 80% for hours.
Tony

Similar Messages

  • Aperture 3: multiple export hangs while generating thumbnails?

    Sigh. I was almost ready to write a blog post claiming that while AP3 has its share of bugs, it's not the unusable mess some have painted it to be. This morning I'm no so sure anymore. I think this is stellar update with tons of potential. When it works it screams on my machine and the new features are amazing. But guys, i need the basics to work.
    Here's what I've just sent t via the feedback form:
    I've been trying to export 29 pictures in web format for the past 40 minutes. I've had to force-quit AP three times and restart my machine twice. Aperture starts exporting at a normal pace but then completely hangs on a "generating thumbnails" process. At this point it becomes impossible to either cancel the task or quit Aperture normally. It also kicks my iMac's fan into overdrive - something that NEVER happens.
    This is not good.
    Other problems:
    - random crashes while using brushes.
    - second display doesn't follow "blank" command and keeps reverting to "alternate" even when the menu says Blank.
    This is a great version of Aperture with a lot of potential. These bugs are killing me though.
    I've just rebuilt the database. If it's still not working I'm going to remove plugins and see if it helps.
    Anyone else having problems with this?

    Absolutely has to be a bug. This isn't a setting or configuration problem. It might even be a Snow Leopard problem. I had the same problems with A2.1.4 on SL as I do with version A3.0.1. Export hangs seem to happen on images that came from my A2 library that was imported into A3 but originally adjusted in A2. These images were imported from scanned TIFF files. If the adjustment mechanism was flawed in prior Aperture versions then Apple needs to create and distribute a utility that converts these images into something that A3 can use.
    I will have to revert to A2 running on Leopard until Apple can get this fixed. If I cannot export, there is no point in running the software. On this discussion thread, we are just trying to fly by flapping our arms.

  • Aperture not building thumbnails

    Having a problem right now with generating thumbnails in Aperture 3.5.1.  Originally had another issue with iMovie seeing very few movies in my Aperture library.  I was able to import all files from all cameras into iMovie, and can see them if I import a sampling of them into another library.  Apple support suggested I rebuild my library, which revealed a few more, but still less than 5% of the total.
    Apple then suggested I create a new library and import my existing library.  I was watching the progress bar near the end when Aperture crashed at completion.  I repaired the library and it began building thumbnails.  The process has been slow, with Aperture running at 100% CPU (one core--single thread?) and very low I/O on the disk.
    The status freezes on one image when Aperture processes roughly 1000 thumbnails.  It says "Generating Thumbnails for [image]" "35,323 Remaining".  At first I thought Aperture may still be processing in the background, seeing how Aperture's CPU utilization remained in the 100% range and disk usage continued.  But when I quit Aperture and restart, it shows barely more progress than what was indicated in the status before quitting Aperture.  The particular images listed are fine, and the thumbnails are generated when Aperture is launched.
    At this point, Aperture will not quit cleanly, or with a Force Quit.  Occasionally I've been able to use this suggestion:
    https://discussions.apple.com/docs/DOC-3881
    In other cases, Aperture seems to quit, but the entry remains in the Activity Monitor, with all accumulated stats, but 0% CPU.  I'm unable to launch Aperture at this time and must restart.  If I try to kill the process, the OS says it can't find it.  Could this be a Mavericks eccentricity?
    When restarting the OS and Aperture, thumbnail generation continues from where it left off, and processes another 1000 images or so.  I did try repairing the database, and thumbnail generation continued, but eventually failed.
    Occasionally, the com.apple.MediaLibraryService stops resonding in the Event Viewer.  This had not always correlated with the frozen progress bar.  In fact, thumbnails have continued to process when I've seen that hang in Event Viewer.  But it always has meant I need to take Aperture down forcefully.  Oddly, I do not have sharing previews enabled (set to never for now).
    There are a few early articles, but they don't seem to offer any suggestions I have not tried, except to persist and restart Aperture each time this happens.  Could take 2-3 weeks at this rate if I need to restart every time the progress bar stops.  I have also tried clearing user and system cache a few times.
    Apple second level support has been slow to respond, and I'm over 9 days into this process.  Has anyone experienced anything similar, or can offer any suggestions?

    Is it only your current Aperture library, that is causing this trouble?
    Or do you see the same problem, when working with a new test library?
    Although otherwise operationally sound, some video in my original library was not viewable in the Media Browser (including iMovie), even after a repair and rebuild.
    I created a new, empty library and imported my original library.  I described that process.  Aside from the crash near the end, it appears to have all my assets.  The project and image counts are the same.
    The issues described about building thumbnails is in this new library.  Upon importing my original library, the new library began generating all new thumbnails.
    If the thumbnail generation is only hanging for your current Aperture library, you may have imported corrupted media - image files, videos that cannot be processed, sound files.
    I know exactly what you're talking about, and this was my first assumption as well.  As an Aperture 3 early adopter, I saw this issue countless times from failed imports.  But I have examined over 8 files that it has apparently hung on.  The thumbnails are fine!  I look at the assets, directly, and they are in perfect condition.  I expected to find corrupted TIFF files or bad thumbnails.  Neither were true.  If I request to generate it again, it works just fine.
    Have you tried to remove the images from your Apeture library, that are shown in the message? Inspect them in the Finder and check the media type - jpeg, raw, video and check, if other Applications can open it.
    Yes.
    I do not have previews generated for nearly 2/3 of the images in my library, although I haven't seen reports about how this could be a problem.
    UPDATE
    Since my first post, I found a suggestion to regenerate all new thumbnails.  Days of time lost, but I restarted.  Still had a crash after about 1000 thumbnails.  com.apple.qtserver or something was hung.  Seemed only to launch occasionally after I restarted.  Thought this might be responsible for generating thumbnails for video.  So I did a search for all video files and let Aperture build these as I browsed through, page by page. 
    Since that time, Aperture has been building thumbnails for 10 hours, the longest run yet.  Thumbnails are still generating VERY slowly, but I haven't seen a crash since.
    Could it be the back and forth between images and video as it's generating thumbnails?

  • Time to build thumbnails on import?

    I am new to Aperture, and have just imported my photo library of 19000 photos into Aperture as referenced files. I know they are referenced because I have the little arrow bottom right.
    I have the preview pref set to not build previews for new projects. I also have the "maintain previews for this project" unchecked.
    The actual import took an hour or so during which it said "importing" next to the cog wheel at the bottom of the window.
    Now it says "thumbnails" in the same place, and has been doing this for a couple of hours now.
    At this point the library is 8 Gb in size but I have no idea how far through the thumbnail building it is.
    I am a bit surprised at the size, since there shouldn't be any previews, and also how long it is taking to build just thumbnails.
    Does what is happening sound correct? How big should a 19K library with no previews be? and how long would you expect the thumbnail building to take?
    I am doing this on my Mac Pro, BTW.
    Thanks for any input.
    PS (edit). When I scroll through the entire 19000 by having the cursor on the top project level in the projects window, the thumbnails appear extremely quickly.
    Also, I assume that if it is building previews instead of thumbnails, it would say "previews" next to the cogwheel?
    Message was edited by: Mike Boreham

    Just discovered the "show Activity" window, which shows that it is building thumbnails (not previews) and that it has 6000 more to do.
    So that probably answers my own questions, unless anyone has any insights, for which I would be very grateful.

  • I was editing vacation photos in aperture 3 all of a sudden the thumbnail disappeared and now all i have is a vertical white line and an orange flag... how do i get my photo back?  thanks

    i was editing vacation photos in aperture 3 all of a sudden the thumbnail disappeared and now all i have is a vertical white line and an orange flag... how do i get my photo back?  thanks

         Hi Frank.
         I have just had jb Atlanta's problem while adjusting the contrast on a photo. I was creating a slideshow at the time. After a lot of reading up I was about to give up when I tried restoring the file to its original settings as you suggested. Bingo!
         However, that would only work for me, if I restored the settings while in the slideshow. All data had 'disappeared' when I attempted to open the photo in its original project folder.
         Hope this is of help. Many thanks.

  • After Upgrading to 10.6.8 my aperture app starts but hangs trying to read the Lib. I removed the old lib and start with new. but still have the problem. 10.6.8 also made my Shark FX7 do the same thing. Any Ideas? Thanks

    After Upgrading to 10.6.8 my aperture app starts but hangs trying to read the Lib. I removed the old lib and start with new. but still have the problem. 10.6.8 also made my Shark FX7 do the same thing. Any Ideas? Thanks

    Verifying volume “Macintosh HD”
    Performing live verification.
    Checking Journaled HFS Plus volume.
    Checking extents overflow file.
    Checking catalog file.
    Checking multi-linked files.
    Checking catalog hierarchy.
    Checking extended attributes file.
    Checking volume bitmap.
    Checking volume information.
    The volume Macintosh HD appears to be OK.

  • How can I stop the Bridge from building Thumbnails?

    I can see it's reading files in from the Server to build thumbnails. But I'd like to interrupt that process because it slows things down too much. I search Preferences to no avail :(

    The best you can do is to have Bridge use the embedded previews by going in to preferences and UNcheck High-quality Previews.
    But the caches still have to be built, though much faster.

  • Imovie 09 never stops building thumbnails-

    greetings,
    this is the first ever launch of imovie 09 on a new macbook pro. there is a 80GB aperture library with lots of short movies taken with various cams and phones…
    now when i launch imovie it tells me that it needs to create thumbnails for my aperture library… and after 18hours still is running (hot) and askes for another 380hours time… what ?!?
    anyone know how to deal with such situation ?
    thanks in advance…
    ab.

    You are welcome.
    In Activity Monitor, left click on the process (iMovie). Then click "Inspect" (second from left at the top).
    A window should come up. In this window, you should see %CPU and "Recent Hangs". If "Recent Hangs" is zero, it is probably working OK. If "Recent Hangs" has a positive number in it, you could be in an infinite loop that will never finish.
    If you need to Force Quit, I would use /Force Quit rather than force quitting from the Activity Monitor. There may be multiple threads that need to be killed.
    Message was edited by: AppleMan1958

  • Aperture 3 trial version hangs and quits

    I downloaded a trial version of Aperture 3 to try it out since I liked the added features. I currently use iPhoto. Everything went fine until I did the iPhoto import.
    Now, every time I start Aperture, it either hangs and becomes unresponsive, or quits before fully opening, or one time opened, said processing, and then quit.
    Another oddity is that my last import in iPhoto now contains a bunch of Aperture graphics and icons. Since I don't have a full serial number, and am not upgrading, I don't know if the other fixes about the serialization would be effective in my case.
    Would love to try Aperture, but so far, no go.

    So I tried downloading 3.0.1 trial that was supposed to fix the unexpected quitting problem. Nope. Still quits. I keep thinking it has something to do with the iPhoto import. Until I did that - or tried to do that, Aperture seemed fine.

  • Building Thumbnails is taking soooo long

    When I first went to open iMovie '08, I'd just finished filming a pair of high school basketball games, and had loaded them into iPhoto. It said it needed to build the thumbnails, and gave me a choice of doing it "now" or "later". I chose to do it now, and proceeded to wait for the next 90 minutes as it ostensibly built the thumbnails. I fiddled around for a bit, then closed iMovie, intending to get back to it later. The next time I opened iMovie, it had to build the thumbnails again! Now these two games fit onto one 4GB SD card. We're not talking about several hundred gigs of video here. Am I honestly going to have to wait for upwards of 90 minutes EVERY TIME I go to use iMovie? Is there a way to save the thumbnails? Help!

    Dan, I feel your pain. Plug in an external hard drive and the program launches into generating thumbnails. Import a second clip from a camera and it generates thumbnails from that clip AND clips already imported! This insane waste of time has ruined this program! I am back to a much older copy of imovie. That is the only way I have figured out how to get a simple movie made quickly! Wasn't that the point, Apple?

  • AP crashing while building thumbnails

    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

    Update:  Ive separated all five years of projects by year and have found a few previews that were bad  and some missing images.  Now my most current Lib is 2013 and crashed importing some images.  Crashed Thread 0 then restaarted and imported fine. 
    Process:         Aperture [252]
    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 [155]
    User ID:         501
    Date/Time:       2013-04-13 13:23:42.949 -0700
    OS Version:      Mac OS X 10.8.3 (12D78)
    Report Version:  10
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000023
    VM Regions Near 0x23:
    -->
        __TEXT                 000000010029e000-00000001009f4000 [ 7512K] r-x/rwx SM=COW  /Applications/Aperture.app/Contents/MacOS/Aperture
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   libobjc.A.dylib                         0x0000000104a984d8 objc_msgSend_vtable4 + 24
    1   com.apple.iLifeSQLAccess                0x00000001042244f7 -[HgModel isEqual:] + 67
    2   com.apple.Aperture                      0x000000010052be54 0x10029e000 + 2678356
    3   com.apple.Aperture                      0x00000001005276f6 0x10029e000 + 2660086
    4   com.apple.Aperture                      0x000000010051e91e 0x10029e000 + 2623774
    5   libdispatch.dylib                       0x000000010788ff01 _dispatch_call_block_and_release + 15
    6   libdispatch.dylib                       0x000000010788c0b6 _dispatch_client_callout + 8
    7   libdispatch.dylib                       0x00000001078910c8 _dispatch_main_queue_callback_4CF + 275
    8   com.apple.CoreFoundation                0x0000000102505b4c __CFRunLoopRun + 1644
    9   com.apple.CoreFoundation                0x00000001025050e2 CFRunLoopRunSpecific + 290
    10  com.apple.HIToolbox                     0x000000010662deb4 RunCurrentEventLoopInMode + 209
    11  com.apple.HIToolbox                     0x000000010662dc52 ReceiveNextEventCommon + 356
    12  com.apple.HIToolbox                     0x000000010662dae3 BlockUntilNextEventMatchingListInMode + 62
    13  com.apple.AppKit                        0x0000000105144563 _DPSNextEvent + 685
    14  com.apple.AppKit                        0x0000000105143e22 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
    15  com.apple.Aperture                      0x0000000100714205 0x10029e000 + 4678149
    16  com.apple.AppKit                        0x000000010513b1d3 -[NSApplication run] + 517
    17  com.apple.prokit                        0x0000000102e156c5 NSProApplicationMain + 378
    18  com.apple.Aperture                      0x00000001002ae4a2 0x10029e000 + 66722
    19  com.apple.Aperture                      0x00000001002addf4 0x10029e000 + 65012
    Thread 1:: Dispatch queue: com.apple.libdispatch-manager
    0   libsystem_kernel.dylib                  0x0000000107aa6d16 kevent + 10
    1   libdispatch.dylib                       0x000000010788edea _dispatch_mgr_invoke + 883
    2   libdispatch.dylib                       0x000000010788e9ee _dispatch_mgr_thread + 54
    Thread 2:
    0   libsystem_kernel.dylib                  0x0000000107aa60fa __psynch_cvwait + 10
    1   libsystem_c.dylib                       0x0000000107935023 _pthread_cond_wait + 927
    2   com.apple.Foundation                    0x00000001045cffe3 -[NSCondition waitUntilDate:] + 357
    3   com.apple.Foundation                    0x00000001045cfe39 -[NSConditionLock lockWhenCondition:beforeDate:] + 235
    4   com.apple.proxtcore                     0x000000010410003a -[XTMsgQueue waitForMessage] + 47
    5   com.apple.proxtcore                     0x00000001040ff282 -[XTThread run:] + 329
    6   com.apple.Foundation                    0x00000001045a4cd2 __NSThread__main__ + 1345
    7   libsystem_c.dylib                       0x00000001079307a2 _pthread_start + 327
    8   libsystem_c.dylib                       0x000000010791d1e1 thread_start + 13
    Thread 23:
    0   libsystem_kernel.dylib                  0x0000000107aa66d6 __workq_kernreturn + 10
    1   libsystem_c.dylib                       0x0000000107932f4c _pthread_workq_return + 25
    2   libsystem_c.dylib                       0x0000000107932d13 _pthread_wqthread + 412
    3   libsystem_c.dylib                       0x000000010791d1d1 start_wqthread + 13
    Thread 0 crashed with X86 Thread State (64-bit):
      rax: 0x0000000000000003  rbx: 0x0000000000000002  rcx: 0x00007fff5f960201  rdx: 0x000000010430fa18
      rdi: 0x00007f9c6f8de600  rsi: 0x00007f9c68400260  rbp: 0x00007fff5f960340  rsp: 0x00007fff5f960318
       r8: 0x0000000000012068   r9: 0x00007fff5f9602a0  r10: 0x00000001197fc800  r11: 0x00007f9c68c32e98
      r12: 0x0000000000000036  r13: 0x0000000104a97240  r14: 0x00007f9c6b278f10  r15: 0x00007f9c6f8de600
      rip: 0x0000000104a984d8  rfl: 0x0000000000010246  cr2: 0x0000000000000023
    Logical CPU: 0
    Binary Images:
           0x10029e000 -        0x1009f3fff  com.apple.Aperture (3.4.3 - 3.4.3) <01A802BA-0100-3F80-947C-A8FEA4726352> /Applications/Aperture.app/Contents/MacOS/Aperture
           0x100c15000 -        0x100c1eff7  com.apple.PhotoFoundation (1.0 - 10.17) <C7921155-5546-33EF-8846-B86721EBA1C4> /Applications/Aperture.app/Contents/Frameworks/PhotoFoundation.framework/Versio ns/A/PhotoFoundation
           0x100c9a000 -        0x1011bafff  com.apple.RedRock (1.9.4 - 310.33) <9B94495A-2267-3684-B6E8-9FE3D4B46495> /Applications/Aperture.app/Contents/Frameworks/RedRock.framework/Versions/A/Red Rock
           0x1014c0000 -        0x101543fff  com.apple.iLifePageLayoutCore (1.0 - 200.9) <8AAC1EB9-5823-3624-A525-635C2A77C34E> /Applications/Aperture.app/Contents/Frameworks/iLifePageLayoutCore.framework/Ve rsions/A/iLifePageLayoutCore
           0x1015a1000 -        0x1015a1fff  com.apple.Cocoa (6.7 - 19) <1F77945C-F37A-3171-B22E-F7AB0FCBB4D4> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
           0x1015a9000 -        0x1015a9fff  com.apple.Carbon (154 - 155) <372716D2-6FA1-3611-8501-3DD1D4A6E8C8> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
           0x1015ad000 -        0x10182dff7  com.apple.AOSKit (1.05 - 152.2) <43361229-45F3-3946-A11A-CC0FF2129F06> /System/Library/PrivateFrameworks/AOSKit.framework/Versions/A/AOSKit
           0x101859000 -        0x10185efff  com.apple.iLifePhotoStreamConfiguration (3.4 - 2.5) <906317D7-09FF-3B77-8F35-01BB74C0109C> /Applications/Aperture.app/Contents/Frameworks/iLifePhotoStreamConfiguration.fr amework/Versions/A/iLifePhotoStreamConfiguration
           0x10186c000 -        0x10189dff7  com.apple.iLifeAssetManagement (2.7 - 40.34) <E4E1A39C-E8AE-31D5-9C50-B392EBAD7447> /Applications/Aperture.app/Contents/Frameworks/iLifeAssetManagement.framework/V ersions/A/iLifeAssetManagement
           0x1018cd000 -        0x1018daff7  com.apple.iphoto.AccountConfigurationPlugin (1.2 - 1.2) <0F515DED-D77E-3E4F-876D-F5CE596A844C> /Applications/Aperture.app/Contents/Frameworks/AccountConfigurationPlugin.frame work/Versions/A/AccountConfigurationPlugin
           0x1018ed000 -        0x101990ff7  com.apple.MobileMe (13 - 1.0.4) <8A990383-9B6C-3CF4-826E-D61373653AB2> /Applications/Aperture.app/Contents/Frameworks/MobileMe.framework/Versions/A/Mo bileMe
           0x101a0c000 -        0x101a0cfff  com.apple.ApplicationServices (45 - 45) <A3ABF20B-ED3A-32B5-830E-B37831A45A80> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
           0x101a13000 -        0x101b9eff7  com.apple.WebKit (8536 - 8536.28.10) <792FA1F3-68F2-36F8-A070-898B3682F5DE> /System/Library/Frameworks/WebKit.framework/Versions/A/WebKit
           0x101c96000 -        0x101f67ff7  com.apple.security (7.0 - 55179.11) <73958084-5BBC-3597-A751-7370B0C247E5> /System/Library/Frameworks/Security.framework/Versions/A/Security
           0x10209c000 -        0x10210afff  com.apple.framework.IOKit (2.0.1 - 755.22.5) <1547DA6F-9793-30A2-8E92-7368DE84D46C> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
           0x10213a000 -        0x1022e8fff  com.apple.QuartzCore (1.8 - 304.2) <234EABE1-067C-3DAE-BEAC-674526E232C2> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
           0x1023a5000 -        0x1023b4fff  com.apple.opengl (1.8.7 - 1.8.7) <26F7FF79-6BB2-3968-B70D-71D4E07C9551> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
           0x1023c3000 -        0x102460ff7  com.apple.PDFKit (2.7.3 - 2.7.3) <5AE5FD4E-658F-38BC-90DD-C2B28E17ED34> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/PDFKit.framew ork/Versions/A/PDFKit
           0x1024cb000 -        0x1024cbfff  com.apple.CoreServices (57 - 57) <9DD44CB0-C644-35C3-8F57-0B41B3EC147D> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
           0x1024d0000 -        0x1026baff7  com.apple.CoreFoundation (6.8 - 744.18) <A60C3C9B-3764-3291-844C-C487ACF77C2C> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
           0x10281e000 -        0x10286fff7  com.apple.SystemConfiguration (1.12.2 - 1.12.2) <A4341BBD-A330-3A57-8891-E9C1A286A72D> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
           0x10289f000 -        0x10289ffff  com.apple.Accelerate (1.8 - Accelerate 1.8) <6AD48543-0864-3D40-80CE-01F184F24B45> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
           0x1028a3000 -        0x1028a9fff  com.apple.DiskArbitration (2.5.2 - 2.5.2) <C713A35A-360E-36CE-AC0A-25C86A3F50CA> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
           0x1028b5000 -        0x1028c2ff7  com.apple.PluginManager (1.7.6 - 55) <9C4EFFC0-1CDC-360B-9294-57E710B2912A> /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
           0x1028d5000 -        0x1028d5fff  com.apple.quartzframework (1.5 - 1.5) <6403C982-0D45-37EE-A0F0-0EF8BCFEF440> /System/Library/Frameworks/Quartz.framework/Versions/A/Quartz
           0x1028df000 -        0x102a50ff7  com.apple.QTKit (7.7.1 - 2599.24) <A2153722-268B-3293-B9E3-CB59273CDE41> /System/Library/Frameworks/QTKit.framework/Versions/A/QTKit
           0x102b5a000 -        0x102cabfff  com.apple.audio.toolbox.AudioToolbox (1.8 - 1.8) <C680EE1A-B4ED-3E77-A08C-DC47922ACA33> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
           0x102d3a000 -        0x102d3affd  com.apple.audio.units.AudioUnit (1.8 - 1.8) <173346B7-614C-380B-8E80-9BD1BE501674> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
           0x102d41000 -        0x102d9eff7  com.apple.audio.CoreAudio (4.1.1 - 4.1.1) <D15F3FB3-BE53-3545-AD37-9A25A597FE3C> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
           0x102dc7000 -        0x102dd8fff  com.apple.AERegistration (1.2 - 401) <16C4537B-4989-3DF7-8263-588F5C882063> /Applications/Aperture.app/Contents/Frameworks/AERegistration.framework/Version s/A/AERegistration
           0x102df7000 -        0x10306dff7  com.apple.prokit (7.3.2 - 1944.10) <41FA1781-64AA-37C2-8CBF-9D72CFD705C0> /System/Library/PrivateFrameworks/ProKit.framework/Versions/A/ProKit
           0x10320b000 -        0x1035affff  com.apple.iLifeSlideshow (3.1 - 1151.4) <61A831CA-B996-3762-B3DD-85A3CB46F28D> /Applications/Aperture.app/Contents/Frameworks/iLifeSlideshow.framework/Version s/A/iLifeSlideshow
           0x103733000 -        0x1039f6ff7  com.apple.AddressBook.framework (7.1 - 1169) <5FFF3765-414A-3633-ADE5-337CD4B9A102> /System/Library/Frameworks/AddressBook.framework/Versions/A/AddressBook
           0x103c4c000 -        0x103c63ff7  com.apple.iLifeFaceRe
    So Im thinking that even though I have reciently reintalled AP and OSX mt lion   I need to do it again?
    Unless you see anyting in the above?  Guess Ill build a new account and see if that improves stability.
    Thanks for input!!!!

  • Hang Form Builder 10.1.2.3 for fmb files more than 2MB at Windows VISTA& 7

    Hi
    When i open fmb files more than 2MB with Form Builder (10.1.2.3) at Windows 7 form builder Hange and Close.
    Please help me if have any configuration or patch for forms builder.
    Regards
    Adel

    hi
    i think thats the VGA card problem check for compitible Driver.
    sarah

  • Aperture 2.1.4 - hanging, loading, bad preview pics.

    Hi,
    I hope that somebody can help me on this topic here. I have recently updated to 10.6.2 and 2.1.4 aperture. But the issue is now, that the RAW/NEF pictures appear terribly 'pixelized' - they appear on the screen in a bad shape, while the JPGs are ok, thumbnails are ok, too. That was not the case before those updates (not sure which of those caused it, really).
    The color ball is turning forever and memory/CPU consumption seems to grow, when trying to display/edit such NEF file (which come from a Nikon D300, btw.).
    Anyone out there, who had a similar issue.
    J.L.

    Thanks for your comments.
    So I have tried the following: repaired access rights, removed plist.prefs + library & rebuilt library -> unfortunately no success, the 'older' imported RAW/NEF images of the D300 still did appear in a bad resolution.
    Then: I have downloaded 3.0 and now it works, it is still loading all the projects, but on the first view, the RAW guys are looking fine now.
    Thanks for your help & have learned a lot here.
    J.L

  • Aperture 3.4.5 crashes when building new Vault.

    I'm using a Macbook Pro 17", and have used Aperture sucessfully since its inception. I'm using 2x 1Tb exernal HDs for my Library and Vault respectively, (nothing else on them).
    Everything went well until I bought my Fuji X-Pro1 camera. Although we had to wait an eternity for compatibility, it eventually appeared. And so did the difficulties. The new version of Aperture won't run on Snow Leopard, which worked so well on my machine. So I updated to 10.8.4 to run Aperture, but of course losing Rosetta in the process. Then I installed the Aperture update, all seemed to go well, but it was unable to update Vault. No problem, I thought: delete Vault and rebuild it. So here I am with a blank 1Tb drive, new Vault setup, and a Library of around 800Gb to backup. Because I'm using a SATA card, it set off at a cracking pace, and all seemed well. Sadly not. Once it got to about 480Gb, it had slowed to a crawl, and eventually crashed. I'm totally at a loss as to what to do:, I've tried Permissions, Techtool, reformatting the drive, everything.
    At present, it's been running for 36 hours and backed up 646Gb, which is further than it has got before... but I'm not holding my breath. When I look at Activity monitor, Aperture is using 1.77Gb of real memory, and an additional 2.6Gb of virtual memory. Since the machine is maxed out at 4Gb, I can't see why the program is using so much RAM, when it is basically just copying files.
    As a professional photographer who works every day and wants to save my changes to Vault every day, this just isn't acceptable. I can use the clone feature in Techtool, but that's hardly the point, is it? Why clone an entire 800Gb, when I've shot two pictures and adjusted three others? Not exactly good for my business.
    Any realistic help would be much appreciated.

    Your error log does not help much - Aperture is not crashing, it is hanging. Waiting for an event that does not happen.
    Has the vault that you cannot update been created by the same Aperture version? Is it a new vault, or a vault that could be updated before? Where is your vault located? What kind of drive (external? NAS?) And what kind of formatting?
    As a test - can you create and update a vault for a new test Aperture library?
    I hope somebody will jump in who can read hang reports. Crash reports are easier to read.
    Regards
    Léonie

  • CS4 crashes when building Thumbnail clips on tracks

    Hello
         I have recently upgraded to Premiere CS4 (4.1) from CS2 just to do HD using XDCAM footage and it consistently crashes on two separate PCs which have been reformatted and reloaded just for video Editing.  I finally was able to find a pattern and a midway solution.  I have to disable displaying thumbnails on the tracks in order for Premiere to work otherwise it stops responding.  This only happens with HD footage.
    I have one PC Dell Workstation 490 8Gb or RAM (Choice of OS. One partition running XP and another Vista 64 Bits)  Plenty of HD space available . Dual Quad Core.  Nvida GX Quadro FX54
    Another PC  Dell Workstation T755 with 12Gb RAM running Vista 64Bits. Quad Core Xeon  Video Card ATI RADEON 4750HD 1Gb. HD 15k RPM
    I have the same problem on both.  If I leave the thumbnails turned on I have to be quick and Zoom into the track in order to avoid having the program build too many thumbnails.  I can reproduce the problem by zooming out of the track while having thumbnails turned on.   The sound will continue to play but video would eventually freeze.
    Has anyone seen this problem?  It sounds like a leak of memory issue but it happens on both PCs with very different configurations.

    From the Video Track Header, you can choose how the Clips display: Name Only (no thumbnails), First Frame Thumbnails, First & Last Frame Thumbnails and All Frames. Most editor choose the first, with no thumbnails displayed.
    At least two things can affect thumbnail response: video card/driver (you have two different), and then Windows Page File. Maybe something to check: video driver updates, and how the Page File is setup and managed. Video drivers would be my first place to look.
    Good luck,
    Hunt

Maybe you are looking for