Sorry but "hardware issue of undeterminable origin that has cropped up and caused all these issues" sounds incomplete to me. It sounds to me like you are running into basic database realities that Apple and many others often choose to pretend do not exist.
1) Have you _exactly_ followed the manual protocol I suggested earlier for looking for page outs? Did manual calculations add to zero? Although Aperture and OS X are engineered to deal with paging out, even a few page-outs can initiate reduced stability on imperfect setups.
2) Have you tried a Referenced-Originals Library located on an underfilled internal hard drive with Originals (Masters) on external drives?
Optimizing on both of the above two items can help larger DBs cope with less than the very strongest hardware.
Item 2 in particular is important. A large Managed-Originals Library can be problematic for hardware that is in any way less than ideal.
Thank you for your input.
As for the "hardware issue: comment was form Apple. I agree it is incomplete and I have a real hard time with it. What they are saying and I don't think they mean to, is that Maverick's or Aperture broke my hardware. I know this is not possible but by saying I have a hardware issue after installing is odd.
I did everything you mentioned except making a referenced instead of managed library. I did try the local managed "test" library on the system drive. It did crash once so I ruled that out.
I have been running Aperture since version 2 this way on this system with out these issues. I don't see how my NON optimal system is the cause. I am not in a position to upgrade to and optimal system with 12 gb or more memore running on an SSD. If my system fits the requirements for Aperture it should run on it. IMHO.
Lastly I tried to find the page outs you mentioned but I could not. Did they change activity monitor with Maverick's?
Thanks everyone for your help.
I appear to be having this problem with a brand new 15" macbook pro (Late 2013 model.) I had the kernel panic crash/reboot multiple times and immediately upgraded to Aperture 3.5.1 when it became available. Still had the crash earlier today.
Having just spent such a large amount of $ on this new computer I would really like to determine if I have a hardware problem or if it is just software that will hopefully be fixed. Aperture is the only program that has caused the kernel panic so far, but is also the program I use more than any other at the moment. I ran the hardware test suite, but it don't seem to find any issues... I will try again tonight. I am wondering if I should try to get this brand new $3k computer replaced while I still can.
Here is a copy of the dump from the latest panic (all of the other kernel panics have been very similar... Page fault with the com.apple.iokit.IOAcceleratorFamily package at the top of the list of kernel extensions in the backtrace.)
Any thoughts? Any help is greatly appreciated!
Sat Nov 16 16:29:28 2013
panic(cpu 4 caller 0xffffff80194db94e): Kernel trap at 0xffffff801930e058, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x0000000000000000, CR3: 0x0000000229b7902e, CR4: 0x00000000001606e0
RAX: 0x0000000000000000, RBX: 0x0000000000000010, RCX: 0x0000000000000b40, RDX: 0x0000000000005a00
RSP: 0xffffff81ed4ebac8, RBP: 0xffffff81ed4ebb00, RSI: 0xffffff80315bc270, RDI: 0x0000000000000000
R8: 0x0000000000006000, R9: 0xffffff803e979f10, R10: 0x0000000000000000, R11: 0xffffffffffffffff
R12: 0xffffff805d8b3c00, R13: 0xffffff80315bc200, R14: 0xffffff80315bc200, R15: 0xffffff805d8b3c00
RFL: 0x0000000000010202, RIP: 0xffffff801930e058, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000000000000, Error code: 0x0000000000000002, Fault CPU: 0x4
Backtrace (CPU 4), Frame : Return Address
0xffffff81ed4eb750 : 0xffffff8019422f69
0xffffff81ed4eb7d0 : 0xffffff80194db94e
0xffffff81ed4eb9a0 : 0xffffff80194f2dc6
0xffffff81ed4eb9c0 : 0xffffff801930e058
0xffffff81ed4ebb00 : 0xffffff7f9ade2f06
0xffffff81ed4ebb50 : 0xffffff7f9ade364e
0xffffff81ed4ebb90 : 0xffffff80198cd01d
0xffffff81ed4ebbf0 : 0xffffff80198cabcf
0xffffff81ed4ebd40 : 0xffffff80194b6088
0xffffff81ed4ebe50 : 0xffffff8019426bb1
0xffffff81ed4ebe80 : 0xffffff80194139b5
0xffffff81ed4ebef0 : 0xffffff801941e003
0xffffff81ed4ebf70 : 0xffffff80194c92ad
0xffffff81ed4ebfb0 : 0xffffff80194f35e6
Kernel Extensions in backtrace:
dependency: com.apple.iokit.IOPCIFamily(2.8)[D7DDC654-8A3E-33FC-B5ED-E756535EBD4D]@0xffffff 7f99ab9000
dependency: com.apple.iokit.IOGraphicsFamily(2.4)[C193403C-110B-31D6-857E-5AFDB7868294]@0xf fffff7f99d55000
BSD process name corresponding to current thread: Aperture
Mac OS version:
Darwin Kernel Version 13.0.2: Sun Sep 29 19:38:57 PDT 2013; root:xnu-2422.75.4~1/RELEASE_X86_64
Kernel UUID: C51C3998-66EA-3C1B-A46E-90943DA76DF4
Kernel slide: 0x0000000019200000
Kernel text base: 0xffffff8019400000
System model name: MacBookPro11,3 (Mac-2BD1B31983FE1663)
System uptime in nanoseconds: 15605008674775
last loaded kext at 5711071188847: com.apple.iokit.IOBluetoothUSBDFU 4.2.1f2 (addr 0xffffff7f9b923000, size 12288)
last unloaded kext at 5875488802884: com.apple.driver.AppleUSBCDC 4.2.1b5 (addr 0xffffff7f9b916000, size 16384)
I have had my Olympus EM1 for well over a year and never had this issue before the Maverick's / Aperture udate.
as a side note, Aperture has been good since updating to 3.5.1 and I used Aperture for about 2 hours last night and it did not crash. There was a moment that I thought I noticed the telltale flicker that occurs a couple seconds before crash but I could not be sure. I closed everything and restarted before it could hang.
If it happens again I'll give it the chance to crash. Just too quick to try to avoid data corruption.
Anyone else finding the 3.5.1 update to be more stable or fix completely?