On fabric.io/crashlytics, we got a lot of UITableView related accessibility crashes. Ive seen it happen when VoiceOver is active.
It also looks like it is only related to iOS 8.1.2 and 8.2. We have not seen any other iOS versions crash on it.
Is anybody else experiencing this issue, or can anybody help?
Thread : Crashed: com.apple.main-thread
0 libobjc.A.dylib 0x0000000196097bd0 objc_msgSend + 16
1 UIKit 0x000000018352b7dc -[UITableViewCellAccessibility _accessibilityReuseChildren:forMockParent:] + 496
2 UIKit 0x000000018353c070 -[UITableViewCellAccessibilityElement tableViewCell] + 260
3 UIKit 0x000000018353ca90 -[UITableViewCellAccessibilityElement isAccessibilityElement] + 24
4 UIAccessibility 0x0000000192723e4c _appendChildrenToArrayStartingAtIndexWithChildren + 352
5 UIAccessibility 0x0000000192723b20 _addAXElementsToArrayFromObject + 1620
6 UIAccessibility 0x000000019272349c _appendVendedAXElementsFromUIElements + 288
7 UIAccessibility 0x0000000192723358 _createAXUIElementsFromUIElements + 160
8 UIAccessibility 0x00000001927221e8 _copyParameterizedAttributeValueCallback + 208
9 AXRuntime 0x000000018aa684c0 _AXXMIGCopyParameterizedAttributeValue + 256
10 AXRuntime 0x000000018aa64248 _XCopyParameterizedAttributeValue + 412
11 AXRuntime 0x000000018aa6f650 mshMIGPerform + 272
12 CoreFoundation 0x00000001850b2548 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 56
13 CoreFoundation 0x00000001850b24a8 __CFRunLoopDoSource1 + 436
14 CoreFoundation 0x00000001850b0428 __CFRunLoopRun + 1640
15 CoreFoundation 0x0000000184fdd1f4 CFRunLoopRunSpecific + 396
16 GraphicsServices 0x000000018e4076fc GSEventRunModal + 168
17 UIKit 0x000000018996e10c UIApplicationMain + 1488
18 deredactie 0x0000000100075400 main (main.m:14)
19 libdyld.dylib 0x0000000196702a08 start + 4
Workaround for fixing this crash which help me below
In fill item method
self.contentView.isAccessibilityElement = YES;
self.contentView.accessibilityLabel = #"some text";
As I've found crash can be reproduced on iOS up 8.0 to 8.2.
Related
Firebase Crashlytics shows a weird crash on iOS app, I can't understand what causing it:
Crashed: com.apple.main-thread
0 LogoQuizAC 0x10047f6a0 _hidden#18_ + 135 (__hidden#957_:135)
1 LogoQuizAC 0x1004771f4 _hidden#17_ + 96 (__hidden#454_:96)
2 LogoQuizAC 0x100477328 _hidden#20_ + 4304712488 (__hidden#456_:4304712488)
3 Foundation 0x19b094b20 __NSFireTimer + 68
4 CoreFoundation 0x199c79fa0 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 32
5 CoreFoundation 0x199c79ba0 __CFRunLoopDoTimer + 1064
6 CoreFoundation 0x199c78ffc __CFRunLoopDoTimers + 328
7 CoreFoundation 0x199c72ee4 __CFRunLoopRun + 1936
8 CoreFoundation 0x199c7221c CFRunLoopRunSpecific + 600
9 GraphicsServices 0x1b183e784 GSEventRunModal + 164
10 UIKitCore 0x19c6b2ee8 -[UIApplication _run] + 1072
11 UIKitCore 0x19c6b875c UIApplicationMain + 168
12 LogoQuizAC 0x1002b503c main + 20 (RLockedCell.swift:20)
13 libdyld.dylib 0x1999326b0 start + 4
How can I figure it out? any strategy of solving this issue?
I try to fix an error on firebase.
My sources are based on objective-c, and "webkit" is a problem in my code
I try and try to find what is cause of it, but I can't. Because these errors appears in a different places but same error.
stack trace : com.apple.main-thread
**EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000000000028**
keyboard_arrow_up
arrow_right 0
WebKit
WebKit::ProcessThrottler::setAssertionType(WebKit::ProcessAssertionType) + 544
I know it has only few clues for finding. Sorry.
My codes have a lot of request datas to Server and response from Server on mainthread.
I expect it occurs this problem but I'm not sure.
Thanks.
full call stack
Crashed: com.apple.main-thread
0 WebKit 0x199361fcc WebKit::ProcessThrottler::setAssertionType(WebKit::ProcessAssertionType) + 544
1 WebKit 0x199361fb4 WebKit::ProcessThrottler::setAssertionType(WebKit::ProcessAssertionType) + 520
2 WebKit 0x199362484 WebKit::ProcessThrottler::sendPrepareToSuspendIPC(WebKit::IsSuspensionImminent) + 596
3 WebKit 0x199367620 WTF::Detail::CallableWrapper<WebKit::ProcessThrottler::setAssertionType(WebKit::ProcessAssertionType)::$_1, void>::call() + 144
4 WebKit 0x199435e40 -[WKProcessAssertionBackgroundTaskManager _notifyAssertionsOfImminentSuspension] + 436
5 WebKit 0x1994364b0 -[WKProcessAssertionBackgroundTaskManager _handleBackgroundTaskExpirationOnMainThread] + 312
6 JavaScriptCore 0x197034278 WTF::Detail::CallableWrapper<WTF::callOnMainAndWait(WTF::Function<void ()>&&, WTF::MainStyle)::$_0, void>::call() + 48
7 JavaScriptCore 0x197049324 WTF::RunLoop::performWork() + 484
8 JavaScriptCore 0x197049f24 WTF::RunLoop::performWork(void*) + 36
9 CoreFoundation 0x18cfdb81c __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28
10 CoreFoundation 0x18cfdb718 __CFRunLoopDoSource0 + 208
11 CoreFoundation 0x18cfdaa28 __CFRunLoopDoSources0 + 268
12 CoreFoundation 0x18cfd4d20 __CFRunLoopRun + 824
13 CoreFoundation 0x18cfd44bc CFRunLoopRunSpecific + 600
14 GraphicsServices 0x1a3ae6820 GSEventRunModal + 164
15 UIKitCore 0x18f981164 -[UIApplication _run] + 1072
16 UIKitCore 0x18f986840 UIApplicationMain + 168
17 MyApp 0x10235f3d0 main + 29 (main.m:29)
18 libdyld.dylib 0x18cc9be40 start + 4
I have been getting crash reports like this for a keyboard extension I have developed and am either confused about how to read the stack trace or why it is occurring or both and I was hoping someone could help me clear this up.
Below is the stack trace:
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0xd15db9df
Thread : Crashed: com.apple.main-thread
0 libobjc.A.dylib 0x37949f66 objc_msgSend + 5
1 UIKit 0x2cd57f05 -[_UIViewControllerTransitionContext completeTransition:] + 52
2 UIKit 0x2d10ac1f __95-[_UIWindowAnimationController _performLayoutAnimationWithContext:windowGeometryUpdatingBlock:]_block_invoke88 + 26
3 UIKit 0x2cc7b8e1 -[UIViewAnimationBlockDelegate _didEndBlockAnimation:finished:context:] + 308
4 UIKit 0x2cc7b4f9 -[UIViewAnimationState sendDelegateAnimationDidStop:finished:] + 184
5 UIKit 0x2cc7b40f -[UIViewAnimationState animationDidStop:finished:] + 70
6 QuartzCore 0x2c660fe7 CA::Layer::run_animation_callbacks(void*) + 234
7 libdispatch.dylib 0x37ecdc6f _dispatch_client_callout + 22
8 libdispatch.dylib 0x37ed9553 _dispatch_main_queue_callback_4CF$VARIANT$mp + 1322
9 CoreFoundation 0x295ac889 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 8
10 CoreFoundation 0x295aafa9 __CFRunLoopRun + 1512
11 CoreFoundation 0x294f69a1 CFRunLoopRunSpecific + 476
12 CoreFoundation 0x294f67b3 CFRunLoopRunInMode + 106
13 GraphicsServices 0x30e911a9 GSEventRunModal + 136
14 UIKit 0x2cca7635 UIApplicationMain + 1440
15 libxpc.dylib 0x3806f9e3 _xpc_objc_main + 706
16 libxpc.dylib 0x38071009 xpc_main + 168
17 Foundation 0x2a3ec289 service_connection_handler + 162
18 PlugInKit 0x32c5ff75 -[PKService run] + 508
19 PlugInKit 0x32c5fc4b +[PKService main] + 58
20 PlugInKit 0x32c5ffa9 +[PKService _defaultRun:arguments:] + 20
21 libextension.dylib 0x371b60c5 NSExtensionMain + 48
22 libdyld.dylib 0x37f0baaf start + 2
In the left column where it lists the libraries (correct term?) I don't see any reference to my code. In other crash logs there is always some reference to a class in my app or something but I don't see that in this one. What does that mean? Is the crash occurring before my code executes and this is an Apple issue I can ignore?
It's an Apple Bug. The keyboard extension I work on has a nearly identical crash report. Fortunately, this only seems to happen on iOS 8, though I have seen a similar one that affects iOS 9.
I would file a bug report with Apple, and include a copy of the stack trace.
About 10+ crash reported by crittercism.
Name: SIGSEGV
Reason: SEGV_MAPERR
Seems it is a UIScrollView/UITableView animating or scrolling issue.
How can I find the root cause?
Stack:
0
libobjc.A.dylib 0x0000000195fafbd0 objc_msgSend + 12
1
UIKit 0x00000001892b1db8 -[UIScrollView(UIScrollViewInternal) _delegateScrollViewAnimationEnded] + 64
2
UIKit 0x00000001892b1d30 -[UIScrollView(UIScrollViewInternal) _scrollViewAnimationEnded:finished:] + 204
3
UIKit 0x0000000189366814 -[UIAnimator stopAnimation:] + 500
4
UIKit 0x0000000189366248 -[UIAnimator(Static) _advanceAnimationsOfType:withTimestamp:] + 332
5
QuartzCore 0x0000000188b4629c CA::Display::DisplayLinkItem::dispatch() + 28
6
QuartzCore 0x0000000188b46134 CA::Display::DisplayLink::dispatch_items() + 320
7
IOKit 0x0000000185921470 IODispatchCalloutFromCFMessage + 372
8
CoreFoundation 0x0000000184712dc4 __CFMachPortPerform + 176
9
CoreFoundation 0x0000000184727a54 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 52
10
CoreFoundation 0x00000001847279b4 __CFRunLoopDoSource1 + 432
11
CoreFoundation 0x0000000184725934 __CFRunLoopRun + 1636
12
CoreFoundation 0x00000001846512d4 CFRunLoopRunSpecific + 392
13
GraphicsServices 0x000000018de676fc GSEventRunModal + 164
14
UIKit 0x0000000189216fac UIApplicationMain + 1484
15
MyApp 0x000000010001d280 main (main.m:14)
16
libdyld.dylib 0x000000019661aa08 start + 0
I've seen this happen when a controller and/or its table is deallocated during an animation. The OS still triggers delegate methods (e.g., -scrollViewDidEndScrollingAnimation: or -scrollViewDidEndDecelerating:) when it finishes with the animation, but because the objects no longer exist things get weird.
The best fix is to nil the delegate in the controller's dealloc method.
I'm using Crittercism (SDK 4.1.2) crash reporting service to catch reports on my iOS app. i've been getting this crash many times and i've no idea why it's happening.
Name: SIGSEGV - Reason: Main
Crashed Thread
0 libobjc.A.dylib 0x397c4b26 objc_msgSend + 6
1 UIKit 0x31965a2d -[UIScrollView(UIScrollViewInternal) _scrollViewAnimationEnded:finished:] + 177
2 UIKit 0x31a0e4b3 -[UIAnimator stopAnimation:] + 471
3 UIKit 0x31a0de9d -[UIAnimator(Static) _advanceAnimationsOfType:withTimestamp:] + 285
4 UIKit 0x31a0dd7d -[UIAnimator(Static) _LCDHeartbeatCallback:] + 53
5 QuartzCore 0x315419cf _ZN2CA7Display15DisplayLinkItem8dispatchEv + 99
6 QuartzCore 0x31541779 _ZN2CA7Display11DisplayLink14dispatch_itemsEyyy + 345
7 IOMobileFramebuffer 0x3411b76d IOMobileFramebufferVsyncNotifyFunc + 105
8 IOKit 0x2fdd9a75 IODispatchCalloutFromCFMessage + 249
9 CoreFoundation 0x2f0b7e21 __CFMachPortPerform + 137
10 CoreFoundation 0x2f0c29df __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 35
11 CoreFoundation 0x2f0c297b __CFRunLoopDoSource1 + 347
12 CoreFoundation 0x2f0c114f __CFRunLoopRun + 1399
13 CoreFoundation 0x2f02bc27 CFRunLoopRunSpecific + 523
14 CoreFoundation 0x2f02ba0b CFRunLoopRunInMode + 107
15 GraphicsServices 0x33cff283 GSEventRunModal + 139
16 UIKit 0x318cf049 UIApplicationMain + 1137
17 AppName 0x000b1fef main + 67
Not sure if this is the case for you, but I've had a similar crash caused by a button in an UIView trying to invoke a callback method on a already released object. The UI was displayed, and then the object was released.