Q: Solution for Aperture 3.5 and OSX 10.9 Maverick's crashing

I feel a bit unsecure whether or not to upgrade to Mavericks as long as there are reports about problems with Aperture on older machines in version 3.5. I currently run Aperture 3.4.5 on my MacBook Pro mid 2009 with 8 GB RAM with OS 10.7.5.

From the discussion I have understood that I have to upgrade to Aperture 3.5 when I upgrade to Mavericks.

Is it safe to upgrade, or is it better to wait.

I've started having crash problems with Aperture 3.5.1 when I try to export a version.  This has started since upgrading to Mavericks.  Seems to be related to the export thread according to this crash log:

Process:         Aperture [7819]

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

Identifier:      com.apple.Aperture

Version:         3.5.1 (3.5.1)

Build Info:      Aperture-451099000000000~1

App Item ID:     408981426

App External ID: 107312636

Code Type:       X86-64 (Native)

Parent Process:  launchd [182]

Responsible:     Aperture [7819]

User ID:         501

Date/Time:       2014-01-10 09:44:58.569 -0700

OS Version:      Mac OS X 10.9.1 (13B42)

Report Version:  11

Anonymous UUID:  7A12164B-1663-47C5-A609-2B1C2AF76516

Sleep/Wake UUID: 70BC0388-F023-4AEB-A8E3-0AE2D5FFB7DB

Crashed Thread:  5  Dispatch queue: Import/Export Thread

Exception Type:  EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000010

VM Regions Near 0x10:

-->

    __TEXT                 0000000107539000-0000000107c71000 [ 7392K] r-x/rwx SM=COW  /Applications/Aperture.app/Contents/MacOS/Aperture

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

0   libsystem_kernel.dylib                  0x00007fff8b43ba1a mach_msg_trap + 10

1   libsystem_kernel.dylib                  0x00007fff8b43ad18 mach_msg + 64

2   com.apple.CoreFoundation                0x00007fff93356315 __CFRunLoopServiceMachPort + 181

3   com.apple.CoreFoundation                0x00007fff93355939 __CFRunLoopRun + 1161

4   com.apple.CoreFoundation                0x00007fff93355275 CFRunLoopRunSpecific + 309

5   com.apple.HIToolbox                     0x00007fff94ba1f0d RunCurrentEventLoopInMode + 226

6   com.apple.HIToolbox                     0x00007fff94ba1cb7 ReceiveNextEventCommon + 479

7   com.apple.HIToolbox                     0x00007fff94ba1abc _BlockUntilNextEventMatchingListInModeWithFilter + 65

8   com.apple.AppKit                        0x00007fff93d2d28e _DPSNextEvent + 1434

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

10  com.apple.Aperture                      0x00000001079a4e61 0x107539000 + 4636257

11  com.apple.AppKit                        0x00007fff93d209cc -[NSApplication run] + 553

12  com.apple.prokit                        0x0000000108d90dca NSProApplicationMain + 333

13  com.apple.Aperture                      0x0000000107548cc0 0x107539000 + 64704

14  com.apple.Aperture                      0x0000000107548664 0x107539000 + 63076

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

0   libsystem_kernel.dylib                  0x00007fff8b440662 kevent64 + 10

1   libdispatch.dylib                       0x00007fff95bc943d _dispatch_mgr_invoke + 239

2   libdispatch.dylib                       0x00007fff95bc9152 _dispatch_mgr_thread + 52

Thread 2:

0   libsystem_kernel.dylib                  0x00007fff8b43fe6a __workq_kernreturn + 10

1   libsystem_pthread.dylib                 0x00007fff8e102f08 _pthread_wqthread + 330

2   libsystem_pthread.dylib                 0x00007fff8e105fb9 start_wqthread + 13

Thread 3:

0   libsystem_kernel.dylib                  0x00007fff8b43fe6a __workq_kernreturn + 10

1   libsystem_pthread.dylib                 0x00007fff8e102f08 _pthread_wqthread + 330

2   libsystem_pthread.dylib                 0x00007fff8e105fb9 start_wqthread + 13

Thread 4:

0   libsystem_kernel.dylib                  0x00007fff8b43fe6a __workq_kernreturn + 10

1   libsystem_pthread.dylib                 0x00007fff8e102f08 _pthread_wqthread + 330

2   libsystem_pthread.dylib                 0x00007fff8e105fb9 start_wqthread + 13

Thread 5 Crashed:: Dispatch queue: Import/Export Thread

0   com.apple.geode                         0x000000010974db2e -[DGRenderIntentColorSpace initWithColorSpace:] + 62

1   com.apple.geode                         0x0000000109751a89 -[DGColorSyncProfile newColorSpaceWithBlackPointCompensation:] + 67

2   com.apple.RedRock                       0x00000001081ca182 +[RKExporter exportVersion:path:preset:fileNamingPolicy:videoPreset:warnOnError:] + 603

3   com.apple.RedRock                       0x00000001082778cc -[RKExporterForVersions performJob:] + 573

4   com.apple.proxtcore                     0x0000000109a5423c -[XTDistributor distributeMessage:] + 664

5   com.apple.proxtcore                     0x0000000109a53a2f -[XTThread handleMessage:] + 337

6   com.apple.proxtcore                     0x0000000109a534b3 __42-[XTDispatchMsgQueue triggerDispatchQueue]_block_invoke + 157

7   libdispatch.dylib                       0x00007fff95bca1d7 _dispatch_call_block_and_release + 12

8   libdispatch.dylib                       0x00007fff95bc72ad _dispatch_client_callout + 8

9   libdispatch.dylib                       0x00007fff95bc968f _dispatch_queue_drain + 451

10  libdispatch.dylib                       0x00007fff95bca9dd _dispatch_queue_invoke + 110

11  libdispatch.dylib                       0x00007fff95bc8fa3 _dispatch_root_queue_drain + 75

12  libdispatch.dylib                       0x00007fff95bca193 _dispatch_worker_thread2 + 40

13  libsystem_pthread.dylib                 0x00007fff8e102ef8 _pthread_wqthread + 314

14  libsystem_pthread.dylib                 0x00007fff8e105fb9 start_wqthread + 13

In all the previous questions, users seem to be experience a different form of crash.  There does not seem to be and specific image file causing the problem.  I shot in RAW format and have never experienced any issues until upgrading the OS.

Any ideas what is going on here?

I just ran some additional tests and it seems the crash ocurrs when the export is set to reduce the image size.  When I export as a full resolution jpg there is no crash.  However when I try to export to fit 1024x1024 the program crashes.  I will investigate further.

Message was edited by: GeorgeB

As a follow up that I tried to post before apple decided to update the communities:

Further research into this shows that the problem is related to the color profile selected for the export version.  If the Adobe RGB Linear profile is selected you get a crash.  If you select the sRGB profile things are fine.  Not sure what the issue is other than Adobe, but this only started happening with the upgrade to OS Mavericks.

Hope this helps the debugging.  Still would like to know why this is the case.

Just throwing in my 2 cents - Aperture was crashing for me, about every third time I ran it, after installing mavericks. The aperture update and the first mavericks update did not fix it. I hadn't really gotten to the point of doing any in-depth research on it yet, but apparently I found a fix - I deleted the Lost & Found folder that was on my boot drive, created during or sometimes after the mavericks install. I'm not sure if this is directly related to whatever got fixed, just know that it hasn't crashed since I deleted that folder.

I seem to have fixed mine to. I did it by pruning the number of programs in my startup (which I didn't choose) right down. Don't know what one was causing it..but who cares!

I am having a similar problem and in reply to Reistad, I would wait until the problem gets fixed. I wish I had been aware of this and other Maverick issues, such as synching data, before I upgraded.

I have Applecare so am in the process of trying out different approaches to the problem with their guidance. I will post if I get it resolved.

"Apple has determined that i have a hardware issue of undeterminable origin that has cropped up and caused all these issue. "

I am having the same problem. What does this mean or what are the implications? Could you resolve this? Did you need to buy a new mac.

My Aperture library just crashes and rebuilds.

My Mac is a top of the range new iMac, so I think the problem is definitely not that. This started heppening after the installation of Mavericks, and I suspect that is where the problem lies. It appears to me that Apple is in denial.

Have installed mavericks

at same time upgraded aperture library

have 4 small aperture libraries which accepted upgrade

Largest library 1.3TB  gets to 6% on upgrade and then quits.

Not sure what the heck to do.

Is there a magic button?

Ihavearabbit - Does Aperture crash or does it just stall. As we've seen posted, large libraries can sometimes take a really long time to upgrade and sometimes it appears it's not responding when in fact it is working. A 1.3TB might take overnight to complete. If it's crashing, then it might be memory. Additional info would help assist.

I think that RAM is the answer.

Aperture uses more and more RAM as you use it. You can see it in the activitiy monitor. I just upgraded my iMac to 32Gb and charged through files. It didn't hang, but the memory usage crept up all the while. There's a bug in Aperture, obviously. If you exit and then re-enter Aperture, it only takes a second and it's back down to base again.

For a while I suggest you leave your Activity Monitor on alongside a reduce Aperture screen and see what happens.

I've done the recent large Mavericks upgrade and Aperture seems better behaved. Anybody else noticing that?

Well so have I but I greatly increased my RAM to 32gb. Ram usage still creeps up, but haven't approached my limit, though it's gone as high as 22gb...