Crash thread 0, AP or bad HD

Question

Level 1

105 points

Crash thread 0, AP or bad HD

I was shooting tethered to a new library and on the third day I had the following crash. Since Im still crashing after all the ht3805 mintenance suggestions that I do on a regular basis..... does this mean my 6month old OWC SSD HD is bad?

Thanks in advance.

DAvid

ps Oh the new lib had three projects and about 150 images in each. I ran Disk utilities from "Command R Start up" and repaired permissions etc which of course were needed. So it seems to be working again but Id like not to have crashes this often.

Process: Aperture [2206]

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

Identifier: com.apple.Aperture

Version: 3.4.4 (3.4.4)

Build Info: Aperture-320085000000000~3

Code Type: X86-64 (Native)

Parent Process: launchd [149]

User ID: 501

Date/Time: 2013-05-10 15:01:04.147 -0700

OS Version: Mac OS X 10.8.3 (12D78)

Report Version: 10

Interval Since Last Report: 335128 sec

Per-App Interval Since Last Report: 309075 sec

Anonymous UUID: C71C4B30-7E65-B442-AAC8-B87788846A44

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

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x000007fd6c15964d

VM Regions Near 0x7fd6c15964d:

IOKit 000000021012a000-0000000212f56000 [ 46.2M] rw-/rw- SM=SHM

-->

JS JIT generated code 000033e718e00000-000033e718e01000 [ 4K] ---/rwx SM=NUL

Application Specific Information:

objc_msgSend() selector name: performSelector:withObject:

Performing @selector(a_stopCapture:) from sender NSProButton 0x7fd6c1006bd0

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

0 libobjc.A.dylib 0x000000010d46b250 objc_msgSend + 16

1 com.apple.AppKit 0x000000010dbf8989 -[NSApplication sendAction:to:from:] + 342

2 com.apple.prokit 0x000000010b7e84ad -[NSProApplication sendAction:to:from:] + 101

3 com.apple.Aperture 0x000000010906e3b7 0x108bf5000 + 4690871

4 com.apple.AppKit 0x000000010dbf87e7 -[NSControl sendAction:to:] + 85

5 com.apple.AppKit 0x000000010dbf871b -[NSCell _sendActionFrom:] + 138

6 com.apple.AppKit 0x000000010dbf6c03 -[NSCell trackMouse:inRect:ofView:untilMouseUp:] + 1855

7 com.apple.AppKit 0x000000010dbf6451 -[NSButtonCell trackMouse:inRect:ofView:untilMouseUp:] + 504

8 com.apple.prokit 0x000000010b82a516 -[NSProButtonCell trackMouse:inRect:ofView:untilMouseUp:] + 507

9 com.apple.AppKit 0x000000010dbf5bcc -[NSControl mouseDown:] + 820

10 com.apple.AppKit 0x000000010dbed53e -[NSWindow sendEvent:] + 6853

11 com.apple.prokit 0x000000010b80bc1d -[NSProPanel sendEvent:] + 244

12 com.apple.AppKit 0x000000010dbe9674 -[NSApplication sendEvent:] + 5761

13 com.apple.prokit 0x000000010b7eaea9 -[NSProApplication sendEvent:] + 1835

14 com.apple.Aperture 0x000000010906e055 0x108bf5000 + 4690005

15 com.apple.AppKit 0x000000010daff24a -[NSApplication run] + 636

16 com.apple.prokit 0x000000010b7eb6c5 NSProApplicationMain + 378

17 com.apple.Aperture 0x0000000108c0552e 0x108bf5000 + 66862

18 com.apple.Aperture 0x0000000108c04e54 0x108bf5000 + 65108

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

0 libsystem_kernel.dylib 0x0000000110480d16 kevent + 10

1 libdispatch.dylib 0x0000000110264dea _dispatch_mgr_invoke + 883

2 libdispatch.dylib 0x00000001102649ee _dispatch_mgr_thread + 54

Thread 2:

0 libsystem_kernel.dylib 0x00000001104800fa __psynch_cvwait + 10

1 libsystem_c.dylib 0x000000011030d023 _pthread_cond_wait + 927

2 com.apple.Foundation 0x000000010cfa5fe3 -[NSCondition waitUntilDate:] + 357

3 com.apple.Foundation 0x000000010cfa5e39 -[NSConditionLock lockWhenCondition:beforeDate:] + 235

4 com.apple.proxtcore 0x000000010cad4c5a -[XTMsgQueue waitForMessage] + 47

5 com.apple.proxtcore 0x000000010cad3ea3 -[XTThread run:] + 329

6 com.apple.Foundation 0x000000010cf7acd2 __NSThread__main__ + 1345

7 libsystem_c.dylib 0x00000001103087a2 _pthread_start + 327

8 libsystem_c.dylib 0x00000001102f51e1 thread_start + 13

Aperture 3, OS X Mountain Lion (10.8.3), AP 3.4.3 2009MBP 8GB ram int ssd

Posted on May 11, 2013 6:59 AM

Reply

Answer 1

Best reply

léonie

Level 10

194,723 points

May 12, 2013 1:32 AM in response to dbmoore

David,

I tried to answer earlier, but I am having troubled to stay signed into ASC.

ps Oh the new lib had three projects and about 150 images in each. I ran Disk utilities from "Command R Start up" and repaired permissions etc which of course were needed. So it seems to be working again but Id like not to have crashes this often.

Did you run "Repair permissions" on your drive from the Recovery Partition before or after you ran Aperture's Library First Aid tools?

Disk Utilities permission repair is o.k. for general documents, but not for photo libraries. For Aperture libraries and iPhoto Libraries the built-in First Aid Tools should be used. After Disk Utilility always run a permission repair with ⌥⌘ on your Aperture library.

objc_msgSend() selector name: performSelector:withObject:

Performing @selector(a_stopCapture:) from sender NSProButton 0x7fd6c1006bd0

Aperture is crashing, when it is trying to perform an action after you pressed a button. What button where you pressing, when the crash occured? There is not much to go on.

Try to narrow the problem down - you know the drill, David:

Check, if it only happens with one particular Aperture library.
Check, if it only happens with certain kinds of images, media, videos. If yes, test these media in other applications.
Check, if it only happens with certain devices (external drives).
Check, if it only happens, when logged into your regular user account. Test from a different account. This will tell us, if it is a system wide problem or something in your account is broken.

Needless to say - if you are suspecting a failing drive, the most important thing to do would be to check your backups, if they are in working condition and update them.

Post back, after the tests.

Regards

Léonie

Reply

Answer 2

dbmoore Author

Level 1

105 points

May 12, 2013 7:55 AM in response to léonie

Hi Leonie I always learn something when I read your responses. Thank you for the time and detail you put in. So that hieroglyphics means button pressed, now I know. Well I cant exactly remember now but it had to be about going back and forth out of full screen, which I did all day. I did run AP repair after the Disk Utilies but didnt know there was an order to do those in, thanks.

Oh how well I know drill! But I must be missing something. Ive must try a new account. It was a new lib with only CR2 raw files captured, I was using a 20ish inch Cinema display as the main monitor. Im this close to getting a imac for the heavy imaging workflow and setting this 2009 mbp out to the email pasture to do easy work.

I still have pageouts going on, I know I had a least 150mb (small) or so every day I was shooting teathered. Also had Mail and Safari opened too but no Photoshop. Wouldnt think that with 8GB ram that would occur and another reason to get a imac for shooting only. I also wonder if the non Apple ram doesnt quit do its full share of work, though tests say its ok.

Thanks for the lessons and help

Cheers

David

Reply

Answer 3

dbmoore Author

Level 1

105 points

May 12, 2013 8:07 AM in response to dbmoore

Oh I was also using an old portable usb mouse from my travel case. And early on before shooting I noticed that I had to unplug my iphone 5 from the usb port to get the camera to resister "on"or ready in thethered mode. Is that cause the phone needs more power? Every thing was pluged into the wall for standard current

Just remembered Ill test the phone thing again on my day off. Thanks

Reply

Answer 4

May 12, 2013 8:08 AM in response to léonie

Aperture is crashing, when it is trying to perform an action after you pressed a button.

Application Specific Information:

objc_msgSend() selector name: performSelector:withObject:

Performing @selector(a_stopCapture:) from sender NSProButton 0x7fd6c1006bd0

Looks like the OP was pressing Stop Capture but as you noted this really tells us nothing. Interacting with any of the UI elements should not cause a crash.

This is on a MBP? Do you have any pointing devices attached or are you just using the trackpad?

Also be aware that running Disk Utilities permission repair will have no affect on this problem. A disk repair from Disk Utility might be worth doing.

You might want to try this in a new user account if you have already tried it with a new library.

regards

Reply

Answer 5

dbmoore Author

Level 1

105 points

May 12, 2013 8:28 AM in response to Frank Caggiano

Thanks Frank!! when I do the Disk utilies repair permissions I always also do disk verify/repair. Thats where it said I had to go to the Recovery Partition to make repairs, then I went back to AP to run Repair. Yes I think I need to finaly do the New Account that Im convinced of now thanks to you and Leonie

cheers

Reply

Answer 6

May 12, 2013 8:33 AM in response to dbmoore

How often are the crashes occurring?

I see you are using a pointing device in addition to the trackpad. Does this device require any software to be installed to use it? Given the crash report it would be worthwhile not using it for a while and if it requires any software to be installed to remove the software.

regards

Reply

Answer 7

dbmoore Author

Level 1

105 points

May 12, 2013 9:28 AM in response to Frank Caggiano

Frank its an old portable usb mouse, MacAlly I think. No software but Ill toss it anyway. Thanks

Reply