Why is aperture crashing on my brand new 27" iMac ?

Question

ie11 Author

Level 1

10 points

Why is aperture crashing on my brand new 27" iMac ?

I just purchased a new 27" imac:

Model Name: iMac

Model Identifier: iMac14,2

Processor Name: Intel Core i7

Processor Speed: 3.5 GHz

Number of Processors: 1

Total Number of Cores: 4

L2 Cache (per Core): 256 KB

L3 Cache: 8 MB

Memory: 16 GB

I purchased this to replace my 2008 MBP whish was too slow for editing large files. I saved up to buy this new machine and am at wit's end already.

I installed Aperture (original disc and upgrade disc, then did upgrade to latest version via ap store.

I imported files from one SD card (less than 900 files) into Aperture. They are on my drive, not an external. I have not even set up time

I have opened iphoto and opened photostream for that, but not for Aperture.

I have not installed any plugins for Aperture--though I own Photomatix and am waiting to install it until this is resolved.

I did not transfer anything from my previous machine, nor use migration assistant as I wanted this to be very clean. I've only set up two email addresses in mail--seriously I'm keeping this machine clean.

SO...My first Aperture session resulted in a spontaneous re-boot. Since then, Aperture has crashed (and I've sent a report) each of the 4 or 5 times I've tried to use it. I'm doing basic things like cropping, viewing with and without the loupe, rotating through view between thumbnails, full screen and

What gives?!

THE WHOLE REASON I SPENT THIS MUCH MONEY IS TO USE APERTURE TO EDIT PHOTOS.

iMac, OS X Mavericks (10.9.1)

Posted on Jan 6, 2014 1:06 PM

Reply

Answer 1

Best reply

léonie

Level 10

195,025 points

Jan 6, 2014 1:23 PM in response to ie11

What does the crash report say? Can you please post the first 50 lines here?

SO...My first Aperture session resulted in a spontaneous re-boot. Since then, Aperture has crashed (and I've sent a report) each of the 4 or 5 times I've tried to use it.

Your download of the update may have been incomplete. I'd reinstall Aperture.

then did upgrade to latest version via ap store.

If you are now running Aperture 3.5.1, then Aperture should be showing as installed in the Purchased tab of the AppStore. In that case you should be able to reinstall by simply deleting Aperture from the "Applications" folder (don't empty the Trash) and then downloading again from the AppStore. Does that work?

Reply

Answer 2

Jan 6, 2014 1:50 PM in response to ie11

Did you try to repair your Aperture Library?

To repair or rebuild your Aperture library

Close Aperture, if it’s open.
Locate the Aperture library you want to fix, then hold down the Command and Option keys while double-clicking the Aperture library.
The Aperture Library First Aid dialog appears.

Reply

Answer 3

ie11 Author

Level 1

10 points

Jan 6, 2014 1:57 PM in response to léonie

I did not copy the crash reports and can't remember how to find them--not something i've had experience with in the past and I'm pretty much self-taught. I guess I'll try deleting it and downloading again.

I did not try to repair the library, given the fact that while doing a repair may fix the continued crashing, is that going to address the problem that caused the original re-boot in the first place? Since the library was brand new at that point.... I thought making changes/adjustments after the fact might cloud the issue with diagnostics. Perhaps not...just that since it's a pretty virginal machine....

Reply

Answer 4

ie11 Author

Level 1

10 points

Jan 6, 2014 1:58 PM in response to ie11

PS thank you both!

Reply

Answer 5

ie11 Author

Level 1

10 points

Jan 6, 2014 2:05 PM in response to ie11

Ha! Found logs: from Saturday:

Process: Aperture [183]

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 [171]

Responsible: Aperture [183]

User ID: 501

Date/Time: 2014-01-04 16:44:05.780 -0600

OS Version: Mac OS X 10.9.1 (13B42)

Report Version: 11

Anonymous UUID: 13109632-D0A3-0107-E2D7-1303EBC00C4F

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

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: EXC_I386_GPFLT

Application Specific Information:

objc_msgSend() selector name: isKindOfClass:

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

0 libobjc.A.dylib 0x00007fff8ec1b097 objc_msgSend + 23

1 com.apple.CoreImage 0x00007fff90f736e1 -[CIFilter setValue:forKey:] + 76

2 com.apple.Aperture 0x0000000104e18400 0x104c1f000 + 2069504

3 com.apple.AppKit 0x00007fff9a91b399 -[NSView _drawRect:clip:] + 3748

4 com.apple.AppKit 0x00007fff9a919c0e -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1799

5 com.apple.AppKit 0x00007fff9a919fea -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2787

6 com.apple.AppKit 0x00007fff9a917a50 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 841

7 com.apple.AppKit 0x00007fff9aa46c03 -[NSNextStepFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 303

8 com.apple.AppKit 0x00007fff9a914209 -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 2828

9 com.apple.AppKit 0x00007fff9a8f363a -[NSView displayIfNeeded] + 1680

10 com.apple.AppKit 0x00007fff9aa3d4ab -[NSNextStepFrame displayIfNeeded] + 156

11 com.apple.AppKit 0x00007fff9a95889e _handleWindowNeedsDisplayOrLayoutOrUpdateConstraints + 884

12 com.apple.AppKit 0x00007fff9af2ccd1 __83-[NSWindow _postWindowNeedsDisplayOrLayoutOrUpdateConstraintsUnlessPostingDisabled]_block_ invoke1331 + 46

13 com.apple.CoreFoundation 0x00007fff909120a7 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23

14 com.apple.CoreFoundation 0x00007fff90912017 __CFRunLoopDoObservers + 391

15 com.apple.CoreFoundation 0x00007fff909037b8 __CFRunLoopRun + 776

16 com.apple.CoreFoundation 0x00007fff90903275 CFRunLoopRunSpecific + 309

17 com.apple.HIToolbox 0x00007fff94a71f0d RunCurrentEventLoopInMode + 226

18 com.apple.HIToolbox 0x00007fff94a71b85 ReceiveNextEventCommon + 173

19 com.apple.HIToolbox 0x00007fff94a71abc _BlockUntilNextEventMatchingListInModeWithFilter + 65

20 com.apple.AppKit 0x00007fff9a7bc28e _DPSNextEvent + 1434

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

22 com.apple.Aperture 0x000000010508ae61 0x104c1f000 + 4636257

23 com.apple.AppKit 0x00007fff9a7af9cc -[NSApplication run] + 553

24 com.apple.prokit 0x0000000106483dca NSProApplicationMain + 333

25 com.apple.Aperture 0x0000000104c2ecc0 0x104c1f000 + 64704

26 com.apple.Aperture 0x0000000104c2e664 0x104c1f000 + 63076

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

0 libsystem_kernel.dylib 0x00007fff993fb662 kevent64 + 10

1 libdispatch.dylib 0x00007fff9930943d _dispatch_mgr_invoke + 239

2 libdispatch.dylib 0x00007fff99309152 _dispatch_mgr_thread + 52

Reply

Answer 6

ie11 Author

Level 1

10 points

Jan 6, 2014 2:07 PM in response to ie11

And today:

Process: Aperture [647]

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 [173]

Responsible: Aperture [647]

User ID: 501

Date/Time: 2014-01-06 14:33:26.261 -0600

OS Version: Mac OS X 10.9.1 (13B42)

Report Version: 11

Anonymous UUID: 13109632-D0A3-0107-E2D7-1303EBC00C4F

Sleep/Wake UUID: B1C06562-012C-41FB-8501-3982E6363FE1

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

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: EXC_I386_GPFLT

Application Specific Information:

objc_msgSend() selector name: isKindOfClass:

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

0 libobjc.A.dylib 0x00007fff8ad76097 objc_msgSend + 23

1 com.apple.CoreImage 0x00007fff8d1da48a FEImageTreeNode::newNode(FETreeContext*, FEImage*) + 114

2 com.apple.CoreImage 0x00007fff8d144fd4 FETreeContext::newImage(FEImage*, CGColorSpace*) + 132

3 com.apple.CoreImage 0x00007fff8d145103 FETreeContext::newImage(FEImage*, CGColorSpace*) + 435

4 com.apple.CoreImage 0x00007fff8d145996 FETreeContext::newSampler(fe_sampler_struct*) + 118

5 com.apple.CoreImage 0x00007fff8d145480 FETreeContext::newImage(FEImage*, CGColorSpace*) + 1328

6 com.apple.CoreImage 0x00007fff8d146209 FETreeContext::renderImage_(FEImage*, CGRect, FEShape const*, CGAffineTransform, CGColorSpace*, FEFormat, bool, void (*)(FEContext*, void*, FEFormat), void (*)(FEContext*, void*), void*) + 493

7 com.apple.CoreImage 0x00007fff8d1468d9 FETreeContext::renderImage(FEImage*, CGRect, FEShape const*, CGAffineTransform, CGColorSpace*, FEFormat, bool, void (*)(FEContext*, void*, FEFormat), void (*)(FEContext*, void*), void*) + 1133

8 com.apple.CoreImage 0x00007fff8d11b8d4 -[FEImage(Internal) _renderWithContext:bounds:transform:colorSpace:format:premultiplied:setupCallba ck:finishCallback:callbackData:] + 280

9 com.apple.CoreImage 0x00007fff8d11b37b -[FEImage renderToContext:bounds:transform:destinationFormat:colorSpace:] + 210

10 com.apple.CoreImage 0x00007fff8d0c7f86 renderImage(FEContext*, CGRect, CGAffineTransform, unsigned int, void*) + 136

11 com.apple.CoreImage 0x00007fff8d1cd988 -[FEOpenCLContext(Buffer) renderUsingGPUWithRenderCallback:destinationFormat:workingFormat:extent:transfo rm:info:] + 556

12 com.apple.CoreImage 0x00007fff8d0c3e6c -[CICLContextImpl renderWithBounds:matrix:function:info:] + 3993

13 com.apple.CoreImage 0x00007fff8d0c8634 -[CIContextImpl render:] + 230

14 com.apple.CoreImage 0x00007fff8d0c65c1 -[CIContext drawImage:inRect:fromRect:] + 1558

15 com.apple.geode 0x000000010f543f13 -[DGOpenGLContext drawImage:fromRect:inRect:dirtyRect:lanczosScale:context:] + 715

16 com.apple.geode 0x000000010f542050 -[DGContext drawImage:fromRect:inRect:dirtyRect:purpose:] + 404

17 com.apple.Aperture 0x000000010d508762 0x10d30f000 + 2070370

18 com.apple.AppKit 0x00007fff96a76399 -[NSView _drawRect:clip:] + 3748

19 com.apple.AppKit 0x00007fff96a74c0e -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1799

20 com.apple.AppKit 0x00007fff96a74fea -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2787

21 com.apple.AppKit 0x00007fff96a72a50 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 841

22 com.apple.AppKit 0x00007fff96ba1c03 -[NSNextStepFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 303

23 com.apple.AppKit 0x00007fff96a6f209 -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 2828

24 com.apple.AppKit 0x00007fff96a4e63a -[NSView displayIfNeeded] + 1680

25 com.apple.AppKit 0x00007fff96b984ab -[NSNextStepFrame displayIfNeeded] + 156

26 com.apple.AppKit 0x00007fff96ab389e _handleWindowNeedsDisplayOrLayoutOrUpdateConstraints + 884

27 com.apple.AppKit 0x00007fff97087cd1 __83-[NSWindow _postWindowNeedsDisplayOrLayoutOrUpdateConstraintsUnlessPostingDisabled]_block_ invoke1331 + 46

28 com.apple.CoreFoundation 0x00007fff8ca6d0a7 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23

29 com.apple.CoreFoundation 0x00007fff8ca6d017 __CFRunLoopDoObservers + 391

30 com.apple.CoreFoundation 0x00007fff8ca5e7b8 __CFRunLoopRun + 776

31 com.apple.CoreFoundation 0x00007fff8ca5e275 CFRunLoopRunSpecific + 309

32 com.apple.HIToolbox 0x00007fff90bccf0d RunCurrentEventLoopInMode + 226

33 com.apple.HIToolbox 0x00007fff90bccb85 ReceiveNextEventCommon + 173

34 com.apple.HIToolbox 0x00007fff90bccabc _BlockUntilNextEventMatchingListInModeWithFilter + 65

35 com.apple.AppKit 0x00007fff9691728e _DPSNextEvent + 1434

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

37 com.apple.Aperture 0x000000010d77ae61 0x10d30f000 + 4636257

38 com.apple.AppKit 0x00007fff9690a9cc -[NSApplication run] + 553

39 com.apple.prokit 0x000000010eb6fdca NSProApplicationMain + 333

40 com.apple.Aperture 0x000000010d31ecc0 0x10d30f000 + 64704

41 com.apple.Aperture 0x000000010d31e664 0x10d30f000 + 63076

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

0 libsystem_kernel.dylib 0x00007fff95556662 kevent64 + 10

1 libdispatch.dylib 0x00007fff9546443d _dispatch_mgr_invoke + 239

2 libdispatch.dylib 0x00007fff95464152 _dispatch_mgr_thread + 52

Reply

Answer 7

léonie

Level 10

195,025 points

Jan 6, 2014 2:24 PM in response to ie11

I did not copy the crash reports and can't remember how to find them-

The application "Console" will find the crash reports for you. The Console is in the subfolder "Utilities" in your Applications folder.

If you launch, click the "Show Log list" icon in the toolbar, if the sidebar with the log files it not showing. The crash report should be listed in the "System diagnostic reports" section of the sidebar or the "User diagnostic report.

Look for logfiles with a recent date and "crash" or "panic" in the name, no "Hang" files, please.

I see, you found your logs already.

Reply

Answer 8

ie11 Author

Level 1

10 points

Jan 6, 2014 2:20 PM in response to léonie

okay, also found this:

Anonymous UUID: 13109632-D0A3-0107-E2D7-1303EBC00C4F

Sat Jan 4 16:31:16 2014

panic(cpu 0 caller 0xffffff80150dc19e): Kernel trap at 0xffffff7f96b68fcc, type 14=page fault, registers:

CR0: 0x000000008001003b, CR2: 0xffffff88384f3ff8, CR3: 0x0000000039239036, CR4: 0x00000000001606e0

RAX: 0x00000000ffffffff, RBX: 0xffffff81e7483800, RCX: 0xffffff80384f4000, RDX: 0xffffff81fc1d00d8

RSP: 0xffffff81e7483790, RBP: 0xffffff81e7483850, RSI: 0xffffff8038572000, RDI: 0xffffff8038504800

R8: 0xffffff81fc1d00d8, R9: 0xffffff80372a0a88, R10: 0x0000000000000000, R11: 0xffffff81e7483698

R12: 0x0000000000000000, R13: 0xffffff8038572000, R14: 0xffffff80389ac000, R15: 0xffffff8038572000

RFL: 0x0000000000010202, RIP: 0xffffff7f96b68fcc, CS: 0x0000000000000008, SS: 0x0000000000000010

Fault CR2: 0xffffff88384f3ff8, Error code: 0x0000000000000000, Fault CPU: 0x0

Backtrace (CPU 0), Frame : Return Address

0xffffff81e7483420 : 0xffffff8015022f69

0xffffff81e74834a0 : 0xffffff80150dc19e

0xffffff81e7483670 : 0xffffff80150f3606

0xffffff81e7483690 : 0xffffff7f96b68fcc

0xffffff81e7483850 : 0xffffff7f96adc8c9

0xffffff81e7483870 : 0xffffff7f96add362

0xffffff81e74838b0 : 0xffffff7f96b688f1

0xffffff81e7483940 : 0xffffff7f96b466fd

0xffffff81e7483990 : 0xffffff7f96b4794d

0xffffff81e74839b0 : 0xffffff7f96b457e3

0xffffff81e74839d0 : 0xffffff7f96b4540e

0xffffff81e7483a10 : 0xffffff7f96acc6de

0xffffff81e7483a40 : 0xffffff7f96ad8031

0xffffff81e7483aa0 : 0xffffff7f96b45fe0

0xffffff81e7483ae0 : 0xffffff7f96acad05

0xffffff81e7483b70 : 0xffffff80154cccda

0xffffff81e7483b90 : 0xffffff80154cd83e

0xffffff81e7483bf0 : 0xffffff80154cb28f

0xffffff81e7483d40 : 0xffffff80150b6008

0xffffff81e7483e50 : 0xffffff8015026bb1

0xffffff81e7483e80 : 0xffffff80150139b5

0xffffff81e7483ef0 : 0xffffff801501e003

0xffffff81e7483f70 : 0xffffff80150c921d

0xffffff81e7483fb0 : 0xffffff80150f3e26

Kernel Extensions in backtrace:

com.apple.iokit.IOAcceleratorFamily(98.7.1)[024BF8EC-2925-3C4B-ADBB-CFE36F7D41C 5]@0xffffff7f96ac1000->0xffffff7f96b19fff

dependency: com.apple.iokit.IOPCIFamily(2.8)[447B4896-16FF-3616-95A2-1C516B2A1498]@0xffffff 7f956ba000

dependency: com.apple.iokit.IOGraphicsFamily(2.3.6)[38E388A5-92D6-3388-B799-F2498E582287]@0 xffffff7f959f2000

com.apple.GeForce(8.1.8)[68DC25D4-7371-3980-BBFB-FD4473EBD8B8]@0xffffff7f96b260 00->0xffffff7f96bb4fff

dependency: com.apple.iokit.IOAcceleratorFamily(98.7.1)[024BF8EC-2925-3C4B-ADBB-CFE36F7D41C 5]@0xffffff7f96ac1000

dependency: com.apple.iokit.IOPCIFamily(2.8)[447B4896-16FF-3616-95A2-1C516B2A1498]@0xffffff 7f956ba000

dependency: com.apple.iokit.IONDRVSupport(2.3.6)[86BA68C6-18DD-30A1-ABF6-54597AD6C277]@0xff ffff7f95a35000

dependency: com.apple.nvidia.driver.NVDAResman(8.1.8)[3A2A3C2D-E129-3190-A682-E831B38F0FBF] @0xffffff7f95a45000

dependency: com.apple.iokit.IOGraphicsFamily(2.3.6)[38E388A5-92D6-3388-B799-F2498E582287]@0 xffffff7f959f2000

BSD process name corresponding to current thread: WindowServer

Mac OS version:

13B42

Kernel version:

Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64

Kernel UUID: 1D9369E3-D0A5-31B6-8D16-BFFBBB390393

Kernel slide: 0x0000000014e00000

Kernel text base: 0xffffff8015000000

System model name: iMac14,2 (Mac-27ADBB7B4CEE8E61)

Reply

Answer 9

léonie

Level 10

195,025 points

Jan 6, 2014 2:50 PM in response to ie11

Looking at the reports you found -

the crashes are all related to graphics:

The first crash in the CoreImage library:
com.apple.CoreImage 0x00007fff90f736e1 -[CIFilter setValue:forKey:] + 76
The second crash in the CoreImage library:

2 com.apple.CoreImage 0x00007fff8d144fd4 FETreeContext::newImage(FEImage*, CGColorSpace*) + 132

The kernel panic happens in the drivers for your graphic cards:

Keep the panic report, just in case there should be a problem with your graphics card

30A1-ABF6-54597AD6C277]@0xff ffff7f95a35000

dependency: com.apple.nvidia.driver.NVDAResman(8.1.8)[3A2A3C2D-E129-3190-A682-E831B38F0FBF] @0xffffff7f95a45000

What these reports do indicate for me is, that your crashes are happening when images need to be processed or renderend on your display. Perhaps you have imported an image or video that cannot be processed or the library needs repairing. Or it could be a problem with the System or your Graphics Card.

Check, if a new Aperture library with some new photos imported will work better. If yes, then your current Aperture library has a problem.

If a new Aperture library does not help, do the reinstall of Aperture. You do not sync with Facebook or Flickr, or any other accounts?

Have you changed any settings in your current user account? If not, reinstall Mavericks, if reinstalling Aperture did not help.

You will need to get your backups setup, before doing a system reinstall.

Post back after testing with the new Aperture library and reinstalling Aperture.

Reply

Answer 10

ie11 Author

Level 1

10 points

Jan 6, 2014 5:49 PM in response to léonie

Thank you so much for the response!

I have not done anything to sync Aperture to anything. I chose not to use it for Flickr or facebook or any other accounts. I have not yet even linked to photostream and I don't plan to. I really want to reserve for serious photography and use iphoto for "recreational" use.

I felt certain that it had crashed more than those two times, but don't see other similar reports. A screen capture shows all the logs.

I really have made few changes since I took the machine from it's box. I have set up the email accounts and imported my contacts, installed Aperture, set up my time capsule for network use and imported 800+photos; I did synch iphoto with my photostream and install the duckduckgo.com plug in for safari, and install firefox as an additional browser, also an updated version of flash.

I will try your suggestions tomorrow after I return home from work and see if they resolve the issue. Many thanks for you kindness!

Reply

Answer 11

léonie

Level 10

195,025 points

Jan 6, 2014 11:31 PM in response to ie11

In the folder "Applications > Utilities" is another diagnostic program "Activity Monitor".

Launch it , before you are starting with Aperture.

In the Activitiy Monitor keep an eye on the "Memory used". If you are seeing, that the processing are using nearly all of the available memory, i.e. 15,9 GB of the 16 GB you are having in your Mac, quit Aperture and restart your system, before everything crashes. Look at this thread:

Aperture 3.5.1 and Mavericks memory leak. https://discussions.apple.com/thread/5590335?start=0&tstart=0

But since your Mac is very new and you probably are still having warranty or Apple Care protection, I'd get the Graphics Card checked at the nearest genius Bar - just to file your problem, while you are still having warranty.

Reply

Answer 12

ie11 Author

Level 1

10 points

Jan 7, 2014 8:23 PM in response to léonie

Thank you SO much. I repaired the aperture library, per instructions, and imported photos from another SD card and worked in both of the projects--the first one and the newly imported one. I have had no issues yet. I will try the activity monitor tomorrow and observe. I'm loath to box it up and transport it to the genius bar, but I will if the activity monitor shows signs. I'll also begin backing up, now that I'm starting to use it!

Again, thank you both SO much for your help, léonie and dfrancefort. Tomorrow I'm going back to editing my F1 photos from November USGP.🙂

Reply

Answer 13

léonie

Level 10

195,025 points

Jan 7, 2014 9:35 PM in response to ie11

O.K. let's keep the fingers crosssed. 🙂

Reply

Answer 14

chris5s

Level 1

55 points

Jan 8, 2014 8:46 AM in response to ie11

I am seeing the same crash on my new (Nov 2013) i7 iMac 27" with AP 3.5.1 :-(

crashlog looks the same:

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

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: EXC_I386_GPFLT

Application Specific Information:

objc_msgSend() selector name: isKindOfClass:

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

0 libobjc.A.dylib 0x00007fff8cd45097 objc_msgSend + 23

1 com.apple.CoreImage 0x00007fff8fe506e1 -[CIFilter setValue:forKey:] + 76

2 com.apple.Aperture 0x000000010aa8c400 0x10a893000 + 2069504

3 com.apple.AppKit 0x00007fff8ad72399 -[NSView _drawRect:clip:] + 3748

4 com.apple.AppKit 0x00007fff8ad70c0e -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:]

my machine has only 8GB RAM, but Aperture never crashed with the same library on my late 2008 MacBook with 8GB. I assume it has to do with the graphics driver.

I've been sending crash logs to Apple for the last couple of days, so hopefully this will get fixed soon.

Reply

Answer 15

ie11 Author

Level 1

10 points

Jan 8, 2014 6:19 PM in response to chris5s

Interesting. We'll hope for the best and keep meeting back here.

Did you try the library repair? DId it work? Hellp for a while?

DId you try anything else?

My prior is also a 2008 MBP (early though) with 8GB. Snap!

Reply