LLDB crash

In our latest two releases we've starte getting sporadic crash reports that I'm having a tough time understanding. Unfortunatly, we haven't been able to reproduce the crash in debug mode with a local build, so we have to do our best to parse the crash report and diagnose from there.At this point in the application, it queries Game Center for matches, sorts them based on latest activity and match status, loads the match data for each match, and then populates a UITableView using custom table view cells.The code complies fine, runs in debug mode on devices and most of the time works in the app that's released in production (only affecting ~10% of users). We've seen it on both iPads and iPhones. In trying to manually reproduce it on my phone, I have been able to get the crash to happen sometimes by pulling down on the table and initiating the refreshControl, other times, just navigating away from the MatchListViewController and returning. Sometimes it seems to happen immediate

My users are experiencing crashes in CoreMedia's FigReadWriteLockLockForRead function and I am unable to reproduce the crash.The stack trace of the crashed thread contains MTAudioProcessingTap, which I am using to process audio coming from multiple video tracks in an AVMutableComposition:Thread: RemoteClientNotifyQueue 0 libsystem_pthread.dylib _pthread_mutex_lock1 CoreMedia FigReadWriteLockLockForRead2 MediaToolbox MTAudioProcessingTapCallbacksServer_NotificationIsPending3 MediaToolbox MTAudioProcessingTapCallbacks_serverHas anyone seen this issue before, or can point me in the right direction for debugging it?

Hello, I have an app which runs ok on iOS7-iOS8.3 on Xcode 6. But when I run it in Xcode 7 it crashes with the following error message and stack trace:*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSProxy doesNotRecognizeSelector:applicationDidBecomeActive:] called!'*** First throw call stack:( 0 CoreFoundation 0x000000010f91a885 __exceptionPreprocess + 165 1 libobjc.A.dylib 0x000000010f393df1 objc_exception_throw + 48 2 CoreFoundation 0x000000010f91a7bd +[NSException raise:format:] + 205 3 CoreFoundation 0x000000010f86fe3a ___forwarding___ + 970 4 CoreFoundation 0x000000010f86f9e8 _CF_forwarding_prep_0 + 120 5 UIKit 0x000000010d988cf2 -[UIApplication _stopDeactivatingForReason:] + 890 6 UIKit 0x000000010d9911b5 -[UIApplication _runWithMainScene:transitionContext:completion:] + 2464 7 UIKit 0x000000010d98e73f -[UIApplication workspaceDidEndTransaction:] + 188 8 FrontBoardServices 0x000000011102dd7b FrontBoardServices + 163195 9 FrontBoardServices 0x0000000

Hello folks,just a question to you all if this only happens to me.I am woundering that I crashed two Apple USB keyboards during a few days on my iMac 21.5 since I installed El Capitan.Both were not longer working after I restarted / rebootet the iMac. 100% damage, also not working on other computers. It might be 100% coincidence OR it might be my iMac.But on the end I had never problem with that on all my Mac´s so I am woundering if an OS could maybe rise up the power on USB ports in a booting process?Any idea is helpful.BTW: why isn´t Apple building and blutooth keyboard with numpad?