Aperture Vault Crash

Hi
I am having some issues with Aperture currently
I'm running Mavericks, 10.9.1 and the latest Aperture (updated yesterday)
When I want to update my vault it always crashes, leaving a beachball etc. This was happening on my previous mac but put it down to it being old, now I have a new macbook pro and it is still happening.
the status bar gets about a quarter full then stops and the beachball spins forever, have tried leaving over night no luck. Have tried repairs and rebuilds but also no luck. Have also tried different drives and new vaults.
Is there anything I can do to make sure my library is being backed up?
thanks

Sounds like the vault might be corrupted. As vaults are just snapshots of the current state of the library I would try making a new one and see if that updates. If it does just abandoned the old vault and use the new.
If the new vault fails also post back.

Similar Messages

Updating Aperture vault will not complete, Aperture quits unexpectedly.

I have a continuing and recurring problem updating Aperture vault after the current Aperture update. The problem also occured after the last update.
Updating the vault does not complete and Aperture quits unexpectedly. This frequently leads to repair to the Aperture library being required. The only solution i have found is to create a new vault. Time consuming and a frustrating waste. I have reloaded Aperture and made updates. This has not solved the problem. I have checked permissions. Nothing wrong there.
My vault and Aperture library are on seperate external drives.

i am experiencing the very same problem updating my vault. Have tried about a half dozen times, creating new vaults (some work some dont) and updating existing vaults (never works). My managed library is 418GB on an external raid array. I have previously created a vault successfully on an external La Cie drive, but then the update failed. After repeated attempts I can not create a new one without Aperture crashing -- which leads to a multi hour repair session. Very very frustraing.
Can someone from Apple comment on whether this is a known bug? What is the work around? Smaller libraries?

Aperture keeps crashing on startup!

I recently moved my library with all referenced master to another 2TB drive. After doing that I imported a dozen of weddings and that took all the night.
After the import was done Aperture just crashes everytime on startup.
I tried with both repairing permission and database with no success, the REBUILD database seems to fix the problem for a while, but then it keeps crashing again just every time.
I don't think it's a drive problem, I run disk utility and at first there was some little problem with the disk which was soon fixed, now the disk is ok and I rebuilt the database several times already... what should I do now?
Anyone has the same problem?
ps. After database rebuild aperture keeps processing files on startup and crashes, what is that processing?
Thank you for your help.
Guido

Hi Frank,
I have a Mac Pro 8 intel core with 16 gig ram, OSX 10.6.8, Aperture 3.1.3.
The problem started presumably after the last import, was roughly 10,000 raw images from a DsmkIII and a mkIV.
No new software or hw installed but the HD which is an hitachi deskstar 7K3000.
After copying the lib and the masters from another drive i normally ran aperture so I guess importing all those images could have caused the problem, but Aperture is supposed to manage great amount of data...
If I create a new library everything works fine. The old library (the one I copied before importing) still works fine.
I get a crash report, never read it but the error code is something like BAD_ACCESS_ and other things..

Aperture constantly crashing - esp. with HDR Efex Pro

I'm running Aperture 3.1.1 and OS 10.6.6. I've deleted the Aperture prefs, rebuilt the photo library, reinstalled Aperture, reinstalled OS 10.6.6, run all of the tests and repairs in Disk Utility and Onyx, and Aperture still crashes at frequent intervals whenever I'm editing - usually when painting something in or out with brushes. By far the most consistent crash is whenever I try to edit a photo with the HDR Efex Pro plug-in. I also get the spinning ball a lot, at fairly random intervals. The funny thing is that the HDR Efex Pro plug-in seems to work fine if I open Aperture in another user account although unfortunately my photo library is in my standard account and I'm reluctant to relocate it just to get a working version of Aperture. I've done everything suggested in Nik's FAQs (eg. deleting duplicate fonts), but nothing works. The Nik people have said I have a corruption in my user file which is beyond the scope of their support. I'm running a 24" 2.8GHz iMac with 4GB of RAM and about 20GB of free hard disk space. Aperture hasn't encountered many problems before recently, so my setup seems to have enough power. I have about 15,000 photos in the library (after importing my iPhoto library recently - by reference only) and the Aperture library is about 140Gb in size. If anyone has any suggestions for a fix, I'd be very grateful as I've run out of ideas. Thanks

Hi, I am no expert in Aperture 3 However just like you I had many issues and crashes of A3. My system is almost identical to yours and my A3 problems were the same as you. Like you, I tried all the fixes but still no luck. Yesterday, I went into my A3 Pref's / Previews & I changed the setting for "share with ilife and iwork" to never.
I haven't had a problem since but only time will tell if this is a total fix.
Good luck,
Art

Backup Storage - Aperture Vault versus Time Machine versus daily SuperDuper

What value does dumping the Aperture library to an Aperture Vault give in addition to running Time Machine to one drive and a daily SuperDuper copy to a second drive with irregular SuperDuper copies to an external drive that can be removed from the machine room.

SImon,
Vault and Time Machine address different needs. Probably you will want to have both.
The advantage of Time Machine: incremental backups of previous versions, very compact storage. And you can integrate it into your regular backup of the whole system and include the regular masters as well. But the disadvantage: Time Machine decides for you, what will be deleted, if the backup drives get full. You do not have control over what will be saved and what not from the previous versions.
The advantage of vaults: You can make full backups of your library for well defined moments in time - snapshots of important states. I'd create a vault, whenever I make a major upgrade of the system at least.
Is there anyway of cancelling a stuck Vault update other than the sledgehammer approach of Force Quit?
If the graphical user interface is unresponsive, like when updating a vault, you can use the Terminal to send the "termination signal" to Aperture: Sometimes this will succeed, even if the "Quit" button does not work:
Look for the Process ID of Aperture in the Activity Monitor (launch Applications > Utilities > Activity Monitor" and click the CPU heading. This will bring Aperture close to the top of the list. Make a note of the PID number in the first column, in this case 66550.
Launch a Terminal window and enter the following command:
kill -TERM 66550 (insert Aperture's PID instead of 66550)
This will send the "Software Termination Signal - TERM to Aperture, the same as pressing the "Quit" button should do, but send it directly, and not from the GUI that is unresponsive. This way I always succeded in cancelling a vaul update without force quitting. Not all processes can be terminated this way, however. The Terminal.app is also in the Applications > Utilities folder.
Regards
Léonie

Aperture Vault and Time Machine

Does anyone know how this will operate ?
Will the Aperture Vault be TM 'unaware' ?
Roger

I guess there'll be a new 'vault' mechanism, as TM backs up your hard drive and vaults typically reside on another drive. whether or not TM can work with other drive I don't know.
Perhaps vaults will remain largely unchanged and be used for recovering entire projects or libraries, and TM will allow you to go back through previous version of the current file, or restore individual images that you may have deleted.
Regards
Steve

Folder labeled "Images Removed from Aperture Vault #1"

Hi all,
I was just looking at everything that's on the External Hard Drive on which I have my Aperture Vault. There's another folder on that EHD labeled "Images Removed from Aperture Vault #1." Noodling through that folder, it seems to be every master that I've deleted, broken down my year, month, and even day.
Is this normal behavior? Can I delete all those sub-folders, etc.? Should I keep the folder itself? Did I somehow set this up initally?
Anyhoo, thank you all for any suggestions.

Yes it is a normal but unreported feature. When you run the vault command the vault created is a snapshot of the current state of the library. If there is a previous vault for this library then images that are in the vault but no longer in the library are moved to the folder you referred to.
If you are certain you do not want any of those images anymore you an delete them.
regard

Aperture 3 crash?

i installed aperture 3 trial, and have been using it for about a day then halfway through editing an image it started to slow and has been ever since. ive restarted my mac twice and managed to delete the image it got stuck on whilst editing but whenever i open the program it continues to say processing? my mac seems ok and has only slowed a little but as soon as i open aperture it crashes?
im not sure what to do, should i delete the aplication from my hard drive or leave the program open?

I too have serious problems with Aperture 3, but with a difference. It loaded correctly on my iMac, and works well - although slowly. I particularly like the new presets and brushes.
However, it crashes on opening, on my MacBook Pro. I did all the usual things, repaired permissions, mended file structures, etc. Re-installe Ap3 - still crashed on opening. So, I tried to reload Aperture 2 - which will not load now, either. So, I used AppZapper, as suggested, which did detect a number of upgrade packages, going back to Aperture 1 and Aperture 2. Eliminating them has made no difference. I am now concerned in case I need to reload Aperture 1 - I am unable to find the original disk!
The really curious part is: how come it works on my iMac, but not on my MacBook Pro? Shouldn't they be the same? Frustrating! Help, please.

Can't create Aperture vault on my new 1 Terrabyte Hard Disk

Just bought two new Maxtor 1 terrabyte harddisks to back-up my Aperture vault,
my Aperture Library is now about 450 Gb. When I'm making a new vault on the new hard-disk, wich takes several hours, my G5 will "colapse" after a few hours, the whole system is stuck and the only way to get out is too get the power of.
When I restart and look at the disk I see that about 250 GB has been transported, I tried this several times and it's always stuck at about the same point. Also when I'm dragging the Aperture-file to the new disk, the same thing happens.
When I do the same thing to a Maxtor 500 GB disk everything worls fine.
Does anybody have a clue ? Thanks in advance !
With kind regards
Albert Brunsting

It could be that the 1TB drive is heating up and shutting down after turning for several hours causing the system to lockup. Might try adding a cooling fan pointed at the external HD.
One alternative is to reduce the library size. Export projects from that large library into another empty one until both are about equal in size. Then back up each library individually onto the external HD.

Time Capsule, Aperture Vault, Folders

I'm considering acquiring a Time Capsule to replace my WD NAS, which is clunky, unreliable, and absurdly slow. My Aperture library seems to constantly become corrupted by my using the NAS both for Time Machine backups and as a duplicate stoarge place for my Vault.
I understand a TC will allow me to backup using Time Machine. But will it also allow me to set up seperate folders, one for an Aperture Vault, and another for storing documents or other material outside of my Mac's hard drive? I also backup incrementally using Superduper and a portanle USB HD. Does anyone know if I could do additional Superduper incremental backups onto a TC? (That's a lot of backing up, I know, but I'm paranoid about losing my stuff)
OSX 10.9.1
Aperture 3.5.1

The TC will have exactly the same issues as the WD NAS.. it is designed specifically for Time Machine.
Constant corruption of a library is due to network disconnections which over wireless are to be expected.. wireless is not a reliable media for holding open files.
You can use the TC to mix files and backups..
See Q3 here.
http://pondini.org/TM/Time_Capsule.html
But I don't see you getting any further down the road to reliable use than you have now.

Aperture vault with no mother library - how do i update it?

hello. i had an aperture library i created for a project. when i was done with the project i created an aperture vault on an external drive. but stupidly i deleted the actual library that created the vault.
now i have a 50g vault on a drive and i need to get back into the library.
when i try and open the vault, it says the vault was created with an older version of aperture and it needs to be updated. but i can't update it. i can't figure out how to even get aperture to recognize the vault at all... what to do?

Simple, effective answer: Yes, make copies of your Libraries as back-ups and don't use the Vault feature.
Vaults are no more than a back-up created from within Aperture. (I suspect Apple added this feature on the assumption that users of Aperture did not regularly back up their data.) They can be problematic (they can also be problem-free). If you are comfortable with Finder or with a program such as SuperDuper or CCC, use it and don't bother with Vaults. (That's what I do, and that's what other top posters here do as well.)
As far as data back-up goes, I recommend that all users maintain at all time three copies of their data. A working copy, a copy of the working copy that gets regularly updated (no less than once a day, unless the data is unchanged), and another copy of the working copy that is kept off-site. Never have all three copies in the same physical location (don't bring your off-site copy on-site. Take your on-site copy off-site, and then bring the off-site copy on-site, effectively swapping them while never having all three copies in the same location).
As for making on Library for each project ... it is generally not recommended. One of the great empowerments of Aperture is that it functions as an index of all the work it contains. I have _every photo I've ever taken_ in my personal Library. I can search my entire oevre. Your needs may be different -- and may be different enough that making one Library for each project you do is sensible -- but using separate Libraries takes the power of this global indexing away. (Fwiw, the reasons I can think of having separate Libraries: image security, image quarantine, multiple photographers, and Libraries of images where the photographer is not important.)
HTH,
--Kirby.
(Sent from my magic glass.)

Nik collection plug-ins are causing aperture to crash. Please help!

Hi everyone, I am running Aperture 3.4.3 and a while back bought Nik Silver Effex 2.0.
A couple of days ago Google emailed me offering the complete Nik Collection for free.
I upgraded but since then everything has been messed up. The plug-ins all appear in aperture but when I try to load them they either fail to load or cause aperture to crash.
I have contacted Nik/Google but all of their suggestions so far have been to no avail.
Please help as I use silver effex professionally and have a job coming up soon that needs black and white edits!
I am desperate here so any help is appreciated.

Nik/Google are trying to work out the issue but have never mentioned any possible compatability issues.
Here is a crash log from trying to operate the viveza plug in
Process:
Aperture [277]
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 [130]
PlugIn Path:
/Library/Application Support/Aperture/*/Viveza2
PlugIn Identifier: com.google.Viveza2.aperture_edit
PlugIn Version:
2.1 (2.100)
Date/Time:
2013-03-30 07:48:00.611 +0000
OS Version:
Mac OS X 10.7.5 (11G63)
Report Version: 9
Interval Since Last Report:
94513 sec
Crashes Since Last Report:
34
Per-App Interval Since Last Report: 13568 sec
Per-App Crashes Since Last Report:   15
Anonymous UUID:
5EADB6B4-F3B5-414C-9592-FCD81A169A8A
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
objc[277]: garbage collection is OFF
Performing @selector(a_editWithPlugIn:) from sender NSMenuItem 0x7ff4b82ceb00
terminate called throwing an exception
abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib
0x000000010b773ce2 __pthread_kill + 10
1   libsystem_c.dylib
0x000000010b6297d2 pthread_kill + 95
2   libsystem_c.dylib
0x000000010b61aa7a abort + 143
3   libc++abi.dylib
0x000000010b4d67bc abort_message + 214
4   libc++abi.dylib
0x000000010b4d3fcf default_terminate() + 28
5   libobjc.A.dylib
0x0000000108d8b1cd _objc_terminate + 114
6   libc++abi.dylib
0x000000010b4d4001 safe_handler_caller(void (*)()) + 11
7   libc++abi.dylib
0x000000010b4d405c std::terminate() + 16
8   libc++abi.dylib
0x000000010b4d5152 __cxa_throw + 114
9   com.google.Viveza2.aperture_edit
0x0000000141a04289 nikHostInterface::getWorkingProfile() + 315675
10 com.google.Viveza2.aperture_edit
0x0000000141a04d3c nikHostInterface::getWorkingProfile() + 318414
11 com.google.Viveza2.aperture_edit
0x0000000141adaf1f boost::detail::get_once_per_thread_epoch() + 736175
12 com.google.Viveza2.aperture_edit
0x0000000141adafed boost::detail::get_once_per_thread_epoch() + 736381
13 com.google.Viveza2.aperture_edit
0x0000000141aa5f74 boost::detail::get_once_per_thread_epoch() + 519172
14 com.google.Viveza2.aperture_edit
0x0000000141a936af boost::detail::get_once_per_thread_epoch() + 443199
15 com.google.Viveza2.aperture_edit
0x00000001416fb75e 0x1414b0000 + 2406238
16 com.google.Viveza2.aperture_edit
0x000000014160f9e8 0x1414b0000 + 1440232
17 com.google.Viveza2.aperture_edit
0x00000001416141bd 0x1414b0000 + 1458621
18 com.google.Viveza2.aperture_edit
0x00000001416c631a 0x1414b0000 + 2188058
19 com.google.Viveza2.aperture_edit
0x00000001416c788e 0x1414b0000 + 2193550
20 com.apple.Aperture
0x00000001048ccc67 0x10467b000 + 2432103
21 com.apple.CoreFoundation
0x00000001068ecefc __invoking___ + 140
22 com.apple.CoreFoundation
0x00000001068ecd94 -[NSInvocation invoke] + 132
23 com.apple.CoreFoundation
0x00000001068ecf64 -[NSInvocation invokeWithTarget:] + 52
24 com.apple.CoreFoundation
0x00000001068e7fa4 ___forwarding___ + 756
25 com.apple.CoreFoundation
0x00000001068e7c38 _CF_forwarding_prep_0 + 232
26 com.google.Viveza2.aperture_edit
0x00000001416c6d83 0x1414b0000 + 2190723
27 com.google.Viveza2.aperture_edit
0x00000001416c7c6b 0x1414b0000 + 2194539
28 com.apple.Aperture
0x00000001048ce3d2 0x10467b000 + 2438098
29 com.apple.Aperture
0x00000001046c5a1c 0x10467b000 + 305692
30 com.apple.CoreFoundation
0x00000001068ea70d -[NSObject performSelector:withObject:] + 61
31 com.apple.AppKit
0x00000001093a98ca -[NSApplication sendAction:to:from:] + 139
32 com.apple.prokit
0x000000010719b7e9 -[NSProApplication sendAction:to:from:] + 100
33 com.apple.Aperture
0x0000000104af22cf 0x10467b000 + 4682447
34 com.apple.AppKit
0x00000001094967ff -[NSMenuItem _corePerformAction] + 399
35 com.apple.AppKit
0x0000000109496536 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 125
36 com.apple.AppKit
0x0000000109735b08 -[NSMenu _internalPerformActionForItemAtIndex:] + 38
37 com.apple.AppKit
0x00000001095c46f9 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 138
38 com.apple.AppKit
0x00000001094109bb NSSLMMenuEventHandler + 339
39 com.apple.HIToolbox
0x000000010a7ab234 _ZL23DispatchEventToHandlersP14EventTargetRecP14OpaqueEventRefP14HandlerCallRec + 1263
40 com.apple.HIToolbox
0x000000010a7aa840 _ZL30SendEventToEventTargetInternalP14OpaqueEventRefP20OpaqueEventTargetRefP14H andlerCallRec + 446
41 com.apple.HIToolbox
0x000000010a7c16db SendEventToEventTarget + 76
42 com.apple.HIToolbox
0x000000010a8077b5 _ZL18SendHICommandEventjPK9HICommandjjhPKvP20OpaqueEventTargetRefS5_PP14OpaqueE ventRef + 398
43 com.apple.HIToolbox
0x000000010a8eee2d SendMenuCommandWithContextAndModifiers + 56
44 com.apple.HIToolbox
0x000000010a9365b5 SendMenuItemSelectedEvent + 253
45 com.apple.HIToolbox
0x000000010a800883 _ZL19FinishMenuSelectionP13SelectionDataP10MenuResultS2_ + 101
46 com.apple.HIToolbox
0x000000010a7f7fc9 _ZL14MenuSelectCoreP8MenuData5PointdjPP13OpaqueMenuRefPt + 600
47 com.apple.HIToolbox
0x000000010a7f7592 _HandleMenuSelection2 + 580
48 com.apple.AppKit
0x00000001093111da _NSHandleCarbonMenuEvent + 250
49 com.apple.AppKit
0x00000001092a6cc9 _DPSNextEvent + 2019
50 com.apple.AppKit
0x00000001092a607d -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 135
51 com.apple.Aperture
0x0000000104af1205 0x10467b000 + 4678149
52 com.apple.AppKit
0x00000001092a29b9 -[NSApplication run] + 470
53 com.apple.prokit
0x000000010719bbe1 NSProApplicationMain + 387
54 com.apple.Aperture
0x000000010468b4a2 0x10467b000 + 66722
55 com.apple.Aperture
0x000000010468adf4 0x10467b000 + 65012
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib
0x000000010b7747e6 kevent + 10
1   libdispatch.dylib
0x000000010b55a786 _dispatch_mgr_invoke + 923
2   libdispatch.dylib
0x000000010b559316 _dispatch_mgr_thread + 54
Thread 2:
0   libsystem_kernel.dylib
0x000000010b773bca __psynch_cvwait + 10
1   libsystem_c.dylib
0x000000010b62b2a6 _pthread_cond_wait + 890
2   com.apple.Foundation
0x0000000108900a5c -[NSCondition waitUntilDate:] + 371
3   com.apple.Foundation
0x00000001088ca22e -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4   com.apple.proxtcore
0x000000010846903a -[XTMsgQueue waitForMessage] + 47
5   com.apple.proxtcore
0x0000000108468282 -[XTThread run:] + 329
6   com.apple.Foundation
0x00000001088d172a -[NSThread main] + 68
7   com.apple.Foundation
0x00000001088d16a2 __NSThread__main__ + 1575
8   libsystem_c.dylib
0x000000010b6278bf _pthread_start + 335
9   libsystem_c.dylib
0x000000010b62ab75 thread_start + 13
Thread 3:
0   libsystem_kernel.dylib
0x000000010b773bca __psynch_cvwait + 10
1   libsystem_c.dylib
0x000000010b62b2a6 _pthread_cond_wait + 890
2   com.apple.Foundation
0x0000000108900a5c -[NSCondition waitUntilDate:] + 371
3   com.apple.Foundation
0x00000001088ca22e -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4   com.apple.proxtcore
0x000000010846903a -[XTMsgQueue waitForMessage] + 47
5   com.apple.proxtcore
0x0000000108468282 -[XTThread run:] + 329
6   com.apple.Foundation
0x00000001088d172a -[NSThread main] + 68
7   com.apple.Foundation
0x00000001088d16a2 __NSThread__main__ + 1575
8   libsystem_c.dylib
0x000000010b6278bf _pthread_start + 335
9   libsystem_c.dylib
0x000000010b62ab75 thread_start + 13
Thread 4:
0   libsystem_kernel.dylib
0x000000010b773bca __psynch_cvwait + 10
1   libsystem_c.dylib
0x000000010b62b2a6 _pthread_cond_wait + 890
2   com.apple.Foundation
0x0000000108900a5c -[NSCondition waitUntilDate:] + 371
3   com.apple.Foundation
0x00000001088ca22e -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4   com.apple.proxtcore
0x000000010846903a -[XTMsgQueue waitForMessage] + 47
5   com.apple.proxtcore
0x0000000108468282 -[XTThread run:] + 329
6   com.apple.Foundation
0x00000001088d172a -[NSThread main] + 68
7   com.apple.Foundation
0x00000001088d16a2 __NSThread__main__ + 1575
8   libsystem_c.dylib
0x000000010b6278bf _pthread_start + 335
9   libsystem_c.dylib
0x000000010b62ab75 thread_start + 13
Thread 5:
0   libsystem_kernel.dylib
0x000000010b773bca __psynch_cvwait + 10
1   libsystem_c.dylib
0x000000010b62b2a6 _pthread_cond_wait + 890
2   com.apple.Foundation
0x0000000108900a5c -[NSCondition waitUntilDate:] + 371
3   com.apple.Foundation
0x00000001088ca22e -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4   com.apple.proxtcore
0x000000010846903a -[XTMsgQueue waitForMessage] + 47
5   com.apple.proxtcore
0x0000000108468282 -[XTThread run:] + 329
6   com.apple.Foundation
0x00000001088d172a -[NSThread main] + 68
7   com.apple.Foundation
0x00000001088d16a2 __NSThread__main__ + 1575
8   libsystem_c.dylib
0x000000010b6278bf _pthread_start + 335
9   libsystem_c.dylib
0x000000010b62ab75 thread_start + 13
Thread 6:
0   libsystem_kernel.dylib
0x000000010b773bca __psynch_cvwait + 10
1   libsystem_c.dylib
0x000000010b62b2a6 _pthread_cond_wait + 890
2   com.apple.Foundation
0x0000000108900a5c -[NSCondition waitUntilDate:] + 371
3   com.apple.Foundation
0x00000001088ca22e -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4   com.apple.proxtcore
0x000000010846903a -[XTMsgQueue waitForMessage] + 47
5   com.apple.proxtcore
0x0000000108468282 -[XTThread run:] + 329
6   com.apple.Foundation
0x00000001088d172a -[NSThread main] + 68
7   com.apple.Foundation
0x00000001088d16a2 __NSThread__main__ + 1575
8   libsystem_c.dylib
0x000000010b6278bf _pthread_start + 335
9   libsystem_c.dylib
0x000000010b62ab75 thread_start + 13
Thread 7:
0   libsystem_kernel.dylib
0x000000010b773bca __psynch_cvwait + 10
1   libsystem_c.dylib
0x000000010b62b2a6 _pthread_cond_wait + 890
2   com.apple.Foundation
0x0000000108900a5c -[NSCondition waitUntilDate:] + 371
3   com.apple.Foundation
0x00000001088ca22e -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4   com.apple.proxtcore
0x000000010846903a -[XTMsgQueue waitForMessage] + 47
5   com.apple.proxtcore
0x0000000108468282 -[XTThread run:] + 329
6   com.apple.Foundation
0x00000001088d172a -[NSThread main] + 68
7   com.apple.Foundation
0x00000001088d16a2 __NSThread__main__ + 1575
8   libsystem_c.dylib
0x000000010b6278bf _pthread_start + 335
9   libsystem_c.dylib
0x000000010b62ab75 thread_start + 13
Thread 8:
0   libsystem_kernel.dylib
0x000000010b773bca __psynch_cvwait + 10
1   libsystem_c.dylib
0x000000010b62b2a6 _pthread_cond_wait + 890
2   com.apple.Foundation
0x0000000108900a5c -[NSCondition waitUntilDate:] + 371
3   com.apple.Foundation
0x00000001088ca22e -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4   com.apple.proxtcore
0x000000010846903a -[XTMsgQueue waitForMessage] + 47
5   com.apple.proxtcore
0x0000000108468282 -[XTThread run:] + 329
6   com.apple.Foundation
0x00000001088d172a -[NSThread main] + 68
7   com.apple.Foundation
0x00000001088d16a2 __NSThread__main__ + 1575
8   libsystem_c.dylib
0x000000010b6278bf _pthread_start + 335
9   libsystem_c.dylib
0x000000010b62ab75 thread_start + 13
Thread 9:: com.apple.NSURLConnectionLoader
0   libsystem_kernel.dylib
0x000000010b77267a mach_msg_trap + 10
1   libsystem_kernel.dylib
0x000000010b771d71 mach_msg + 73
2   com.apple.CoreFoundation
0x000000010688750c __CFRunLoopServiceMachPort + 188
3   com.apple.CoreFoundation
0x000000010688fc74 __CFRunLoopRun + 1204
4   com.apple.CoreFoundation
0x000000010688f486 CFRunLoopRunSpecific + 230
5   com.apple.Foundation
0x00000001088dcfd7 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 335
6   com.apple.Foundation
0x00000001088d172a -[NSThread main] + 68
7   com.apple.Foundation
0x00000001088d16a2 __NSThread__main__ + 1575
8   libsystem_c.dylib
0x000000010b6278bf _pthread_start + 335
9   libsystem_c.dylib
0x000000010b62ab75 thread_start + 13
Thread 10:: com.apple.CFSocket.private
0   libsystem_kernel.dylib
0x000000010b773df2 __select + 10
1   com.apple.CoreFoundation
0x00000001068d8c8b __CFSocketManager + 1355
2   libsystem_c.dylib
0x000000010b6278bf _pthread_start + 335
3   libsystem_c.dylib
0x000000010b62ab75 thread_start + 13
Thread 11:: Dispatch queue: com.apple.Mercury.KDatabaseMgr
0   libsystem_kernel.dylib
0x000000010b774a8e pread + 10
1   com.apple.iLifeSQLAccess
0x000000010855195d seekAndRead + 86
2   com.apple.iLifeSQLAccess
0x00000001085518c9 unixRead + 31
3   com.apple.iLifeSQLAccess
0x000000010856c0db readDbPage + 447
4   com.apple.iLifeSQLAccess
0x000000010856b7df sqlite3PagerAcquire + 342
5   com.apple.iLifeSQLAccess
0x000000010856b64b btreeGetPage + 30
6   com.apple.iLifeSQLAccess
0x0000000108579031 getAndInitPage + 66
7   com.apple.iLifeSQLAccess
0x0000000108579443 moveToChild + 68
8   com.apple.iLifeSQLAccess
0x00000001085793de moveToLeftmost + 90
9   com.apple.iLifeSQLAccess
0x0000000108565f2b sqlite3VdbeExec + 25447
10 com.apple.iLifeSQLAccess
0x000000010855f8ca sqlite3_step + 2420
11 com.apple.iLifeSQLAccess
0x0000000108587afb -[HgKResultSet next] + 262
12 com.apple.iLifeSQLAccess
0x00000001085c23dc __53-[HgEntity insertIntoRidList:idsForColumn:fromQuery:]_block_invoke_0 + 113
13 libdispatch.dylib
0x000000010b559368 _dispatch_function_recurse_invoke + 40
14 libdispatch.dylib
0x000000010b55ac75 _dispatch_barrier_sync_f_invoke + 33
15 libdispatch.dylib
0x000000010b55afba _dispatch_barrier_sync_f_slow + 201
16 com.apple.iLifeSQLAccess
0x00000001085b9cb6 -[HgEntity _dispatch_sync_if_needed_suspend:withBlock:] + 255
17 com.apple.iLifeSQLAccess
0x00000001085c22dd -[HgEntity insertIntoRidList:idsForColumn:fromQuery:] + 431
18 com.apple.iLifeSQLAccess
0x00000001085be745 -[HgEntity selectDistinctList:fromQuery:] + 242
19 com.apple.iLifeSQLAccess
0x00000001085ac201 -[HgIterator requery] + 121
20 com.apple.iLifeSQLAccess
0x0000000108608880 -[HgIterator initWithQuery:returning:] + 592
21 com.apple.iLifeSQLAccess
0x00000001085bc18c -[HgEntity iteratorFromQuery:] + 72
22 com.apple.iLifeSQLAccess
0x00000001085bd35a -[HgEntity setForColumn:fromQuery:] + 48
23 com.apple.iLifeSQLAccess
0x00000001085bca7d -[HgEntity modelUuidsWhere:] + 190
24 com.apple.RedRock
0x000000010524325d -[RKCgImageDataEntity _determineAllUuidsWithImageData] + 55
25 libdispatch.dylib
0x000000010b558a82 _dispatch_call_block_and_release + 18
26 libdispatch.dylib
0x000000010b55a2d2 _dispatch_queue_drain + 264
27 libdispatch.dylib
0x000000010b55a12e _dispatch_queue_invoke + 54
28 libdispatch.dylib
0x000000010b559928 _dispatch_worker_thread2 + 198
29 libsystem_c.dylib
0x000000010b6293da _pthread_wqthread + 316
30 libsystem_c.dylib
0x000000010b62ab85 start_wqthread + 13
Thread 12:
0   libsystem_kernel.dylib
0x000000010b773bca __psynch_cvwait + 10
1   libsystem_c.dylib
0x000000010b62b2a6 _pthread_cond_wait + 890
2   com.apple.Foundation
0x0000000108900a5c -[NSCondition waitUntilDate:] + 371
3   com.apple.Foundation
0x00000001088ca22e -[NSConditionLock lockWhenCondition:beforeDate:] + 251
4   com.apple.proxtcore
0x000000010846903a -[XTMsgQueue waitForMessage] + 47
5   com.apple.proxtcore
0x0000000108468282 -[XTThread run:] + 329
6   com.apple.Foundation
0x00000001088d172a -[NSThread main] + 68
7   com.apple.Foundation
0x00000001088d16a2 __NSThread__main__ + 1575
8   libsystem_c.dylib
0x000000010b6278bf _pthread_start + 335
9   libsystem_c.dylib
0x000000010b62ab75 thread_start + 13
Thread 13:
0   libsystem_kernel.dylib
0x000000010b773bca __psynch_cvwait + 10
1   libsystem_c.dylib
0x000000010b62b274 _pthread_cond_wait + 840
2   com.google.Viveza2.aperture_edit
0x00000001419dc3f2 nikHostInterface::getWorkingProfile() + 152196
3   com.google.Viveza2.aperture_edit
0x00000001419ed5ee nikHostInterface::getWorkingProfile() + 222336
4   com.google.Viveza2.aperture_edit
0x0000000141a21d70 boost::thread::start_thread() + 382
5   libsystem_c.dylib
0x000000010b6278bf _pthread_start + 335
6   libsystem_c.dylib
0x000000010b62ab75 thread_start + 13
Thread 14:
0   libsystem_kernel.dylib
0x000000010b773bca __psynch_cvwait + 10
1   libsystem_c.dylib
0x000000010b62b274 _pthread_cond_wait + 840
2   com.google.Viveza2.aperture_edit
0x00000001419dc3f2 nikHostInterface::getWorkingProfile() + 152196
3   com.google.Viveza2.aperture_edit
0x00000001419ed5ee nikHostInterface::getWorkingProfile() + 222336
4   com.google.Viveza2.aperture_edit
0x0000000141a21d70 boost::thread::start_thread() + 382
5   libsystem_c.dylib
0x000000010b6278bf _pthread_start + 335
6   libsystem_c.dylib
0x000000010b62ab75 thread_start + 13
Thread 15:
0   libsystem_kernel.dylib
0x000000010b773bca __psynch_cvwait + 10
1   libsystem_c.dylib
0x000000010b62b274 _pthread_cond_wait + 840
2   com.google.Viveza2.aperture_edit
0x00000001419dc3f2 nikHostInterface::getWorkingProfile() + 152196
3   com.google.Viveza2.aperture_edit
0x00000001419ed5ee nikHostInterface::getWorkingProfile() + 222336
4   com.google.Viveza2.aperture_edit
0x0000000141a21d70 boost::thread::start_thread() + 382
5   libsystem_c.dylib
0x000000010b6278bf _pthread_start + 335
6   libsystem_c.dylib
0x000000010b62ab75 thread_start + 13
Thread 16:
0   libsystem_kernel.dylib
0x000000010b773bca __psynch_cvwait + 10
1   libsystem_c.dylib
0x000000010b62b274 _pthread_cond_wait + 840
2   com.google.Viveza2.aperture_edit
0x00000001419dc3f2 nikHostInterface::getWorkingProfile() + 152196
3   com.google.Viveza2.aperture_edit
0x00000001419ed5ee nikHostInterface::getWorkingProfile() + 222336
4   com.google.Viveza2.aperture_edit
0x0000000141a21d70 boost::thread::start_thread() + 382
5   libsystem_c.dylib
0x000000010b6278bf _pthread_start + 335
6   libsystem_c.dylib
0x000000010b62ab75 thread_start + 13
Thread 17:
0   libsystem_kernel.dylib
0x000000010b773bca __psynch_cvwait + 10
1   libsystem_c.dylib
0x000000010b62b274 _pthread_cond_wait + 840
2   com.google.Viveza2.aperture_edit
0x00000001419dc3f2 nikHostInterface::getWorkingProfile() + 152196
3   com.google.Viveza2.aperture_edit
0x00000001419ed87f nikHostInterface::getWorkingProfile() + 222993
4   com.google.Viveza2.aperture_edit
0x0000000141a21d70 boost::thread::start_thread() + 382
5   libsystem_c.dylib
0x000000010b6278bf _pthread_start + 335
6   libsystem_c.dylib
0x000000010b62ab75 thread_start + 13
Thread 18:
0   libsystem_kernel.dylib
0x000000010b773bca __psynch_cvwait + 10
1   libsystem_c.dylib
0x000000010b62b274 _pthread_cond_wait + 840
2   com.google.Viveza2.aperture_edit
0x00000001419dc3f2 nikHostInterface::getWorkingProfile() + 152196
3   com.google.Viveza2.aperture_edit
0x00000001419ed87f nikHostInterface::getWorkingProfile() + 222993
4   com.google.Viveza2.aperture_edit
0x0000000141a21d70 boost::thread::start_thread() + 382
5   libsystem_c.dylib
0x000000010b6278bf _pthread_start + 335
6   libsystem_c.dylib
0x000000010b62ab75 thread_start + 13
Thread 19:
0   libsystem_kernel.dylib
0x000000010b773bca __psynch_cvwait + 10
1   libsystem_c.dylib
0x000000010b62b274 _pthread_cond_wait + 840
2   com.google.Viveza2.aperture_edit
0x00000001419dc3f2 nikHostInterface::getWorkingProfile() + 152196
3   com.google.Viveza2.aperture_edit
0x00000001419ed87f nikHostInterface::getWorkingProfile() + 222993
4   com.google.Viveza2.aperture_edit
0x0000000141a21d70 boost::thread::start_thread() + 382
5   libsystem_c.dylib
0x000000010b6278bf _pthread_start + 335
6   libsystem_c.dylib
0x000000010b62ab75 thread_start + 13
Thread 20:
0   libsystem_kernel.dylib
0x000000010b774192 __workq_kernreturn + 10
1   libsystem_c.dylib
0x000000010b629594 _pthread_wqthread + 758
2   libsystem_c.dylib
0x000000010b62ab85 start_wqthread + 13
Thread 21:
0   libsystem_kernel.dylib
0x000000010b774192 __workq_kernreturn + 10
1   libsystem_c.dylib
0x000000010b629594 _pthread_wqthread + 758
2   libsystem_c.dylib
0x000000010b62ab85 start_wqthread + 13
Thread 22:
0   libsystem_kernel.dylib
0x000000010b774192 __workq_kernreturn + 10
1   libsystem_c.dylib
0x000000010b629594 _pthread_wqthread + 758
2   libsystem_c.dylib
0x000000010b62ab85 start_wqthread + 13
Thread 23:
0   libsystem_kernel.dylib
0x000000010b774192 __workq_kernreturn + 10
1   libsystem_c.dylib
0x000000010b629594 _pthread_wqthread + 758
2   libsystem_c.dylib
0x000000010b62ab85 start_wqthread + 13
Thread 24:
0   libsystem_kernel.dylib
0x000000010b774192 __workq_kernreturn + 10
1   libsystem_c.dylib
0x000000010b629594 _pthread_wqthread + 758
2   libsystem_c.dylib
0x000000010b62ab85 start_wqthread + 13
Thread 25:
0   libsystem_kernel.dylib
0x000000010b773bca __psynch_cvwait + 10
1   libsystem_c.dylib
0x000000010b62b274 _pthread_cond_wait + 840
2   com.google.Viveza2.aperture_edit
0x00000001419dc3f2 nikHostInterface::getWorkingProfile() + 152196
3   com.google.Viveza2.aperture_edit
0x00000001415ccdbd 0x1414b0000 + 1166781
4   com.google.Viveza2.aperture_edit
0x0000000141a21d70 boost::thread::start_thread() + 382
5   libsystem_c.dylib
0x000000010b6278bf _pthread_start + 335
6   libsystem_c.dylib
0x000000010b62ab75 thread_start + 13
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x00007fff642766d8 rdx: 0x0000000000000000
rdi: 0x000000000000f603 rsi: 0x0000000000000006 rbp: 0x00007fff64276700 rsp: 0x00007fff642766d8
   r8: 0x000000010b6bdfb8   r9: 0x0000000000000374 r10: 0x000000010b773d0a r11: 0xffffff80002dad60
r12: 0x00007ff4b85223e8 r13: 0x00007fff64276960 r14: 0x000000010b6c0960 r15: 0x00007fff64276850
rip: 0x000000010b773ce2 rfl: 0x0000000000000206 cr2: 0x000000010aa2b000
Logical CPU: 0
Binary Images:
0x10467b000 -
0x104dd0fff com.apple.Aperture (3.4.3 - 3.4.3) <01A802BA-0100-3F80-947C-A8FEA4726352> /Applications/Aperture.app/Contents/MacOS/Aperture
0x104ff4000 -
0x104ffdff7 com.apple.PhotoFoundation (1.0 - 10.17) <C40F985F-9C0A-389A-9E21-684EB0A5B160> /Applications/Aperture.app/Contents/Frameworks/PhotoFoundation.framework/Versio ns/A/PhotoFoundation
0x105075000 -
0x105595fff com.apple.RedRock (1.9.4 - 310.33) <9B94495A-2267-3684-B6E8-9FE3D4B46495> /Applications/Aperture.app/Contents/Frameworks/RedRock.framework/Versions/A/Red Rock
0x10589a000 -
0x10591dfff com.apple.iLifePageLayoutCore (1.0 - 200.9) <8AAC1EB9-5823-3624-A525-635C2A77C34E> /Applications/Aperture.app/Contents/Frameworks/iLifePageLayoutCore.framework/Ve rsions/A/iLifePageLayoutCore
0x10597b000 -
0x10597bfff com.apple.Cocoa (6.6 - ???) <021D4214-9C23-3CD8-AFB2-F331697A4508> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x105983000 -
0x105983fff com.apple.Carbon (153 - 153) <895C2BF2-1666-3A59-A669-311B1F4F368B> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x105987000 -
0x105bf3ff7 com.apple.AOSKit (1.021 - 94) <530546F3-F01C-3A89-8477-C800EFE59593> /System/Library/PrivateFrameworks/AOSKit.framework/Versions/A/AOSKit
0x105c0e000 -
0x105c13fff com.apple.iLifePhotoStreamConfiguration (3.4 - 2.5) <906317D7-09FF-3B77-8F35-01BB74C0109C> /Applications/Aperture.app/Contents/Frameworks/iLifePhotoStreamConfiguration.fr amework/Versions/A/iLifePhotoStreamConfiguration
0x105c1c000 -
0x105c1fff7 libCoreFSCache.dylib (??? - ???) <0D155750-7910-32C5-8327-924FC1089442> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache .dylib
0x105c23000 -
0x105c54ff7 com.apple.iLifeAssetManagement (2.7 - 40.34) <E4E1A39C-E8AE-31D5-9C50-B392EBAD7447> /Applications/Aperture.app/Contents/Frameworks/iLifeAssetManagement.framework/V ersions/A/iLifeAssetManagement
0x105c88000 -
0x105c95ff7 com.apple.iphoto.AccountConfigurationPlugin (1.2 - 1.2) <0F515DED-D77E-3E4F-876D-F5CE596A844C> /Applications/Aperture.app/Contents/Frameworks/AccountConfigurationPlugin.frame work/Versions/A/AccountConfigurationPlugin
0x105caa000 -
0x105d4dff7 com.apple.MobileMe (13 - 1.0.4) <9A7FCC99-67CE-3F5E-98BB-9079B305087F> /Applications/Aperture.app/Contents/Frameworks/MobileMe.framework/Versions/A/Mo bileMe
0x105dcb000 -
0x105dcbfff com.apple.ApplicationServices (41 - 41) <03F3FA8F-8D2A-3AB6-A8E3-40B001116339> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
0x105dce000 -
0x105f58ff7 com.apple.WebKit (7534.57 - 7534.57.7) <15AA1A2E-DCAC-35CE-89DF-0FF7149198CD> /System/Library/Frameworks/WebKit.framework/Versions/A/WebKit
0x106044000 -
0x106339ff7 com.apple.security (7.0 - 55148.6) <4535E500-973A-3BA7-AF65-DF5CF0658F02> /System/Library/Frameworks/Security.framework/Versions/A/Security
0x10645a000 -
0x1064c5ff7 com.apple.framework.IOKit (2.0 - ???) <FE838BB6-D42E-3291-A1A0-6F53FC970261> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x1064f7000 -
0x106697ff7 com.apple.QuartzCore (1.7 - 270.5) <19E5E0AB-DAA9-3F97-988C-D9A46AFB9C04> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x106744000 -
0x106753fff com.apple.opengl (1.8.1 - 1.8.1) <51B34133-CEE3-3FC6-82AC-ADF567AE673C> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x10675b000 -
0x1067eefff com.apple.PDFKit (2.6.5 - 2.6.5) <9CC30317-E89D-3DDF-9069-F3A9CEE4B9A1> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/PDFKit.framew ork/Versions/A/PDFKit
0x106852000 -
0x106852fff com.apple.CoreServices (53 - 53) <043C8026-8EDD-3241-B090-F589E24062EF> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x106857000 -
0x106a2bff7 com.apple.CoreFoundation (6.7.2 - 635.21) <62A3402E-A4E7-391F-AD20-1EF20236CE1B> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x106b7e000 -
0x106bcaff7 com.apple.SystemConfiguration (1.11.3 - 1.11) <0A7F1982-B4EA-3424-A0C7-FE46C6224F03> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x106bfb000 -
0x106bfbfff com.apple.Accelerate (1.7 - Accelerate 1.7) <82DDF6F5-FBC3-323D-B71D-CF7ABC5CF568> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x106c01000 -
0x106c07fff com.apple.DiskArbitration (2.4.1 - 2.4.1) <CEA34337-63DE-302E-81AA-10D717E1F699> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x106c11000 -
0x106c1ffff com.apple.PluginManager (1.7.6 - 55) <ABA41202-6D4F-368A-BE19-BD1729AF074A> /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
0x106c34000 -
0x106c34fff com.apple.quartzframework (1.5 - 1.5) <21FCC91F-C7B9-304F-8C9C-04F3924F4AE3> /System/Library/Frameworks/Quartz.framework/Versions/A/Quartz
0x106c3d000 -
0x106dc8ff7 com.apple.QTKit (7.7.1 - 2339) <2BC2CF44-CEAF-3D3B-A250-CA59D6AFB0B0> /System/Library/Frameworks/QTKit.framework/Versions/A/QTKit
0x106ecc000 -
0x107029fff com.apple.audio.toolbox.AudioToolbox (1.7.3 - 1.7.3) <5F1E4695-BC74-3ADD-8345-627BCD68201A> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x1070af000 -
0x1070affff com.apple.audio.units.AudioUnit (1.7.3 - 1.7.3) <04C10813-CCE5-3333-8C72-E8E35E417B3B> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x1070bc000 -
0x107124ff7 com.apple.audio.CoreAudio (4.0.3 - 4.0.3) <9987DC46-2A96-3BA0-B88B-04E573C0AD9B> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x107151000 -
0x107162fff com.apple.AERegistration (1.2 - 401) <16C4537B-4989-3DF7-8263-588F5C882063> /Applications/Aperture.app/Contents/Frameworks/AERegistration.framework/Version s/A/AERegistration
0x10717d000 -
0x1073f8ff7 com.apple.prokit (7.2.3 - 1823) <0D6BA804-8262-3942-B84D-B4886082242F> /System/Library/PrivateFrameworks/ProKit.framework/Versions/A/ProKit
0x10757b000 -
0x10791ffff com.apple.iLifeSlideshow (3.1 - 1151.4) <61A831CA-B996-3762-B3DD-85A3CB46F28D> /Applications/Aperture.app/Contents/Frameworks/iLifeSlideshow.framework/Version s/A/iLifeSlideshow
0x107aa3000 -
0x107dc8ff7 com.apple.AddressBook.framework (6.1.3 - 1091) <5A8BEED1-229C-3A9C-8281-581127A1B9B5> /System/Library/Frameworks/AddressBook.framework/Versions/A/AddressBook
0x107fbb000 -
0x107fd2ff7 com.apple.iLifeFaceRecognition (1.0 - 30.11) <46E3C666-EE15-324E-85D0-E56ECA0A342D> /Applications/Aperture.app/Contents/Frameworks/iLifeFaceRecognition.framework/V ersions/A/iLifeFaceRecognition
0x107fe6000 -
0x108074fff com.apple.iLifeMediaBrowser (2.6.4 - 502.4.5) <A19798B7-E1A6-3117-8094-8D3A2CAB417F> /System/Library/PrivateFrameworks/iLifeMediaBrowser.framework/Versions/A/iLifeM ediaBrowser
0x1080d6000 -
0x10810fff7 com.apple.fayray.PrintServices (20120703 - 11.6) <33FDFA8A-D41E-36A6-AB42-58FBE1F4D751> /Applications/Aperture.app/Contents/Frameworks/PrintServices.framework/Versions /A/PrintServices
0x108149000 -
0x10817dff7 com.apple.ProUtils (1.1 - 200.36) <BA3481EC-8808-36B1-A88E-7FE9ECC08319> /Applications/Aperture.app/Contents/Frameworks/ProUtils.framework/Versions/A/Pr oUtils
0x10819c000 -
0x108395fff com.apple.geode (1.5.3 - 270.7) <ED680AB8-EBEB-3CBA-9D07-B5B21407A984> /Applications/Aperture.app/Contents/Frameworks/Geode.framework/Versions/A/Geode
0x108465000 -
0x1084dfff7 com.apple.proxtcore (1.4.1 - 250.56) <623B61AC-BA2D-3420-83A2-D083E128C726> /Applications/Aperture.app/Contents/Frameworks/ProXTCore.framework/Versions/A/P roXTCore
0x10854a000 -
0x108664fff com.apple.iLifeSQLAccess (1.7.1 - 60.5) <1E1D3528-A309-363F-93AD-D2B5B1115DE6> /Applications/Aperture.app/Contents/Frameworks/iLifeSQLAccess.framework/Version s/A/iLifeSQLAccess
0x1086d2000 -
0x1086d4fff com.apple.ExceptionHandling (1.5 - 10) <06CC4716-FB75-3CD7-A1ED-ECA2A07F2926> /System/Library/Frameworks/ExceptionHandling.framework/Versions/A/ExceptionHand ling
0x1086de000 -
0x108706ff7 com.apple.iPhoto.Tellus (1.3 - 70.18) <585F6DDC-2C06-3C23-B029-9E7E00CCBCB7> /Applications/Aperture.app/Contents/Frameworks/Tellus.framework/Versions/A/Tell us
0x10872a000 -
0x108753ff7 com.apple.iPhoto.Tessera (1.1 - 70.18) <9974FE70-E381-3FD0-ABDD-F3EAAB1B99C8> /Applications/Aperture.app/Contents/Frameworks/Tessera.framework/Versions/A/Tes sera
0x108770000 -
0x1087cbfff com.apple.ImageCaptureCore (3.1.0 - 3.1.0) <9F7C4D81-5CC7-3D66-AC66-81EA9A5EAB94> /System/Library/Frameworks/ImageCaptureCore.framework/Versions/A/ImageCaptureCo re
0x10880c000 -
0x108814ff7 com.apple.AEProfiling (1.2 - 23) <AF1D815F-B5F7-316B-91C1-9C4FCAF13BBF> /Applications/Aperture.app/Contents/Frameworks/AEProfiling.framework/Versions/A /AEProfiling
0x108823000 -
0x108841fef com.apple.XSKey (1.0.0 - 52) <6B090A2B-D9A5-9D21-0DF6-AE40A775B60B> /Library/Frameworks/XSKey.framework/Versions/A/XSKey
0x108858000 -
0x108865fff com.apple.CrashReporterSupport (10.7.4 - 353) <6044CFB6-939E-3C73-BFBB-A8BBC096F135> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/Cra shReporterSupport
0x108877000 -
0x108b90fff com.apple.Foundation (6.7.2 - 833.25) <22AAC369-B63C-3C55-8AC6-C3ECBA44DA7B> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x108d74000 -
0x108e58e5f libobjc.A.dylib (228.0.0 - compatibility 1.0.0) <871E688B-CF57-3BC7-80D6-F6476DFF109B> /usr/lib/libobjc.A.dylib
0x108e72000 -
0x108ee5fff libstdc++.6.dylib (52.0.0 - compatibility 7.0.0) <6BDD43E4-A4B1-379E-9ED5-8C713653DFF2> /usr/lib/libstdc++.6.dylib
0x108f4a000 -
0x108f77fe7 libSystem.B.dylib (159.1.0 - compatibility 1.0.0) <DA79E5BA-BBA3-3768-AAD8-B34BA877EF03> /usr/lib/libSystem.B.dylib
0x108f89000 -
0x1091b3fe7 com.apple.CoreData (104.1 - 358.14) <6BB64605-8DA7-337D-A2AB-A3346A421CBD> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x10929e000 -
0x109ea4fff com.apple.AppKit (6.7.5 - 1138.51) <44417D02-6123-3FC3-A119-CE51BB4C3006> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x10a52f000 -
0x10a553fff com.apple.RemoteViewServices (1.5 - 44.2) <A0417D7F-22E9-3FD8-AC55-67654D8E93EB> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/Remot eViewServices
0x10a57b000 -
0x10a5ebfff com.apple.datadetectorscore (3.0 - 179.4) <9C01D16F-75A9-3BDD-B91A-F0F32261A2E7> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDe tectorsCore
0x10a628000 -
0x10a741fff com.apple.DesktopServices (1.6.5 - 1.6.5) <5E7DD5F4-B4DA-3F75-A14A-3494E81CFBA0> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
0x10a7a3000 -
0x10aacffff com.apple.HIToolbox (1.9 - ???) <CCB32DEA-D0CA-35D1-8019-E599C8007AB6> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
0x10ac1c000 -
0x10ac27ff7 com.apple.speech.recognition.framework (4.0.21 - 4.0.21) <6540EAF2-E3BF-3D2E-B4C1-F106180D6F20> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogni tion.framework/Versions/A/SpeechRecognition
0x10ac34000 -
0x10ac82fff libauto.dylib (??? - ???) <D8AC8458-DDD0-3939-8B96-B6CED81613EF> /usr/lib/libauto.dylib
0x10ac9a000 -
0x10ae9cfff libicucore.A.dylib (46.1.0 - compatibility 1.0.0) <0176782F-9526-3905-813A-7A5676EC2C86> /usr/lib/libicucore.A.dylib
0x10af30000 -
0x10b032fff libxml2.2.dylib (10.3.0 - compatibility 10.0.0) <AFBB22B7-07AE-3F2E-B88C-70BEEBFB8A86> /usr/lib/libxml2.2.dylib
0x10b060000 -
0x10b072ff7 libz.1.dylib (1.2.5 - compatibility 1.0.0) <30CBEF15-4978-3DED-8629-7109880A19D4> /usr/lib/libz.1.dylib
0x10b07d000 -
0x10b0e5ff7 com.apple.coreui (1.2.2 - 165.11) <9316266A-39CA-3EC7-9C9E-726462CEFF4D> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
0x10b126000 -
0x10b127fff liblangid.dylib (??? - ???) <CACBE3C3-2F7B-3EED-B50E-EDB73F473B77> /usr/lib/liblangid.dylib
0x10b12f000 -
0x10b146fff com.apple.MultitouchSupport.framework (231.4 - 231.4) <10A978D1-8781-33F0-BE45-60C9171F7278> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/Multit ouchSupport
0x10b156000 -
0x10b157fff libDiagnosticMessagesClient.dylib (??? - ???) <3DCF577B-F126-302B-BCE2-4DB9A95B8598> /usr/lib/libDiagnosticMessagesClient.dylib
0x10b161000 -
0x10b189fff com.apple.PerformanceAnalysis (1.11 - 11) <8D4C6382-DD92-37A2-BCFC-E89951320848> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/Perf ormanceAnalysis
0x10b1aa000 -
0x10b1c6ff7 com.apple.GenerationalStorage (1.0 - 126.1) <509F52ED-E54B-3FEF-B3C2-759387B826E6> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/Gene rationalStorage
0x10b1d2000 -
0x10b339fff com.apple.CFNetwork (520.5.1 - 520.5.1) <08F70E26-5456-3BFB-8192-00D3CE40D3C9> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
0x10b3df000 -
0x10b3f2ff7 libCRFSuite.dylib (??? - ???) <034D4DAA-63F0-35E4-BCEF-338DD7A453DD> /usr/lib/libCRFSuite.dylib
0x10b3fb000 -
0x10b471ff7 libc++.1.dylib (28.4.0 - compatibility 1.0.0) <A24FC3DA-4FFA-3DD2-9DCC-2B8D1B3BF97C> /usr/lib/libc++.1.dylib
0x10b4ce000 -

Is there a need for Aperture Vaults if I'm using Time Machine and/or SuperDuper?

Hey all
What's the benefit of Aperture Vaults if I'm using Time Machine or SuperDuper for my regular backups?
John

John,
Aperture vaults are snapshots of a certain moment. So you can create a collections of vaults saved at specific intervalls, say one each year, or before you upgrade your system. If you keep your older vaults, you will be able to restore images from many years back. If your library is huge, you may only notice years later that an important image got corrupted.
Time machine backups are very convenient and you can go back in time easily, but you can never be sure, how much back in time your backup will go. You have no control over which older versions will be deleted, when TM runs out of space.
Clones are great, i.e. if you create bootable clones. This way you will be able to revert to a previous system without reinstalling. With respect to Aperture libraries cloning your library will give you the same benefits as vaults.
My experience tells me, that a mixture is good. If you can, keep three backups, and not all in the same place.
I keep one backup at my office and two at home. I have a bootable clone, a TimeMachine backup, and occasionally create a new vault. My most important images are in my dropbox and synced to all my macs.
regards
Léonie

Aperture vault is freezing at 50% when updating!

I really need help on this! My aperture vault only seems to freeze and the progress bar is stuck at about 50%. I have to force quit aperture when this happens. I tried to make a new vault on a noter external disk. It is no help. I have a very powerful iMac. i7 SSD only one year old. Aperture version 3.3. The external disk is formated Mac OS Extended (journalført - norwegian Lion 10.7.4).
This is bothering me very!!!!
Someone!?

Hi,
If you have followed all the methods mentioned in "Aperture 3: Troubleshooting Basics" http://support.apple.com/kb/HT3805?viewlocale=en_US&locale=en_US (repair and rebuild etc.) then I would advice to wait and let it work longer. It may seem to get stuck but if you wait (not 5 minutes but 5 or 20 hours) it may go through.
I have already had years issue that taking Vault backup takes tens of hours. I have tried all tricks mentioned in this forum (if you search you should find 20-30 threads about Vault being slow, freezing etc.). Everybody here knows better and says that it should not take that long and will advice you to do this and that, but if you look at those 20-30 threads not even half have resolution for the person who had the issue.
I'm backing up the library instead, from SSD to HD it takes 15 minutes with CCC (block copy including verify), and faster from SSD to SSD. Here is thread I opened to ask if this is OK:
https://discussions.apple.com/message/18877353#18877353
Best Regards,
Samuli

Aperture vault is full

Aperture Vaults.
Aperture 3.3.2
I have a 500gb vault that is now full, if I install another 500gb vault, will aperture continue to updated the new vault with my additional data or will it just fill that with all the original data then tell me that’s full?
Thanks.

Pharaoh,
Unless there are other things on the disk that you can move/delete then you have 3 options: (1) Get a larger drive, set it up inside Aperture and back up to it. This approach will take some time as going to a new drive will require Aperture to back up everything rather than just incremental changes (which is what it does normally). (2) Split your libraries into 2 or more and back the new one up to another (new) drive. (3) Don't use a vault as a backup. NOT recommended. A 1 TB drive is no more or less likely to fail than say a 500MB (assuming equal quality in manufacturing). Aperture vaults do not know how to "span" more than one drive - so far as I can tell.
Personally, I use two work drives (that only contain the library) and alternate between them for increased performance. One library will of course be behind the other at any given moment but has everything from the last overwrite. No matter which drive I work from, they both backup to the same vault drive.
To be honest, high performance large capacity drives have become quite affordable. I consider using 3 drives in this manner to provide a reasonable level of security without going into RAID or other solutions.
HTH
Robert

Aperture Vault Crash

Similar Messages

Maybe you are looking for