WebKitLegacy - [_WebSafeForwarder forwardInvocation:] application crash in iOS10.0.1 - uiwebview

I am getting the following crash only in iOS10.0.1. Its not giving me enough stack trace information. The only clue I have is , seems to be happening from WebView.Because it says "WebKitLegacy - [_WebSafeForwarder forwardInvocation:] ".
The crash log is given below. I have another crash group related to "updateSubviewsOfScrollContentViews" seems like all are related.
Any suggestions on this very helpful. Like how to debug this issue ? Where might be the problem?
Exception Type: SIGSEGV
Exception Codes: SEGV_ACCERR at 0xcec18beb8
Crashed Thread: 0
Application Specific Information:
objc_msgSend() selector name: addObject:
Thread 0 Crashed:
0 libobjc.A.dylib 0x000000018d9fef30 objc_msgSend + 16
1 UIKit 0x000000019502abd8 updateSubviewsOfScrollContentViews + 184
2 UIKit 0x000000019502acdc updateSubviewsOfScrollContentViews + 444
3 UIKit 0x000000019502acdc updateSubviewsOfScrollContentViews + 444
4 UIKit 0x000000019502acdc updateSubviewsOfScrollContentViews + 444
5 UIKit 0x000000019502acdc updateSubviewsOfScrollContentViews + 444
6 UIKit 0x000000019502aad0 -[UIWebBrowserView _collectAdditionalSubviews] + 380
7 UIKit 0x000000019502a924 -[UIWebDocumentView _updateSubviewCaches] + 52
8 UIKit 0x000000019500d268 -[UIWebDocumentView webViewDidCommitCompositingLayerChanges:] + 44
9 UIKit 0x000000019500cf80 -[UIWebBrowserView webViewDidCommitCompositingLayerChanges:] + 80
10 CoreFoundation 0x000000018efba160 __invoking___ + 140
11 CoreFoundation 0x000000018eeadc3c -[NSInvocation invoke] + 280
12 CoreFoundation 0x000000018eeb26ec -[NSInvocation invokeWithTarget:] + 56
13 WebKitLegacy 0x0000000194ae77f8 -[_WebSafeForwarder forwardInvocation:] + 152
14 libdispatch.dylib 0x000000018de3d200 _dispatch_call_block_and_release + 20
15 libdispatch.dylib 0x000000018de3d1c0 _dispatch_client_callout + 12
16 libdispatch.dylib 0x000000018de41d6c _dispatch_main_queue_callback_4CF + 996
17 CoreFoundation 0x000000018ef61f2c __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 8
18 CoreFoundation 0x000000018ef5fb18 __CFRunLoopRun + 1656
19 CoreFoundation 0x000000018ee8e048 CFRunLoopRunSpecific + 440
20 GraphicsServices 0x0000000190911198 GSEventRunModal + 176
21 UIKit 0x0000000194e67818 -[UIApplication _run] + 680
22 UIKit 0x0000000194e62550 UIApplicationMain + 204
23 Essentials 0x00000001000f5f08 main (main.m:52)
24 ??? 0x000000018de705b8 0x0 + 0enter code here

Related

Crash in iOS 13 when using EAAccessoryManager -showBluetoothAccessoryPickerWithNameFilter:completion

We are getting the following crashes on iOS 13 (only), when using the -showBluetoothAccessoryPickerWithNameFIlter:completion: method of EAAccessoryManager
In Crashlytics crash reports, the top of the stack trace shows this: [BluetoothDevice classicDevice] doesNotRecognizeSelector:
This is a typical stack trace:
Last Exception Backtrace:
0 CoreFoundation 0x1aeb68a48 __exceptionPreprocess + 220
1 libobjc.A.dylib 0x1ae88ffa4 objc_exception_throw + 55
2 CoreFoundation 0x1aea6c5a8 -[NSObject+ 193960 (NSObject) doesNotRecognizeSelector:] + 139
3 CoreFoundation 0x1aeb6caf4 ___forwarding___ + 1323
4 CoreFoundation 0x1aeb6ea7c _CF_forwarding_prep_0 + 91
5 BluetoothSettings 0x1d8836b00 -[BTAlert showAlertWithResult:] + 1047
6 CoreFoundation 0x1aeac4288 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 19
7 CoreFoundation 0x1aeac42d0 ___CFXRegistrationPost1_block_invoke + 63
8 CoreFoundation 0x1aeac3630 _CFXRegistrationPost1 + 367
9 CoreFoundation 0x1aeac32e8 ___CFXNotificationPost_block_invoke + 103
10 CoreFoundation 0x1aea3f59c -[_CFXNotificationRegistrar find:object:observer:enumerator:] + 1415
11 CoreFoundation 0x1aeac2c38 _CFXNotificationPost + 1243
12 Foundation 0x1aee1f138 -[NSNotificationCenter postNotificationName:object:userInfo:] + 59
13 Foundation 0x1aef5122c __NSThreadPerformPerform + 231
14 CoreFoundation 0x1aeae6a00 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 23
15 CoreFoundation 0x1aeae6958 __CFRunLoopDoSource0 + 79
16 CoreFoundation 0x1aeae60f0 __CFRunLoopDoSources0 + 179
17 CoreFoundation 0x1aeae123c __CFRunLoopRun + 1079
18 CoreFoundation 0x1aeae0adc CFRunLoopRunSpecific + 463
19 GraphicsServices 0x1b8a66328 GSEventRunModal + 103
20 UIKitCore 0x1b2bdbae0 UIApplicationMain + 1935
21 Jolt 0x100c7dc10 main + 2808848 (main.m:52)
22 libdyld.dylib 0x1ae96a360 start + 3

Crash in MetalContext with Xamarin

We have a crash in MetalContext with over 3000 crashes in a single day on iOS 10 devices only. We are unable to track down the root of the error and google reveals nobody else have the same issue. Is there anyone who has any clues to where we can begin to look?
CRASH_INFO_ENTRY_0
Assertion failed: (_mcimpl->device == [_mcimpl->queue device]), function MetalContext, file /BuildRoot/Library/Caches/com.apple.xbs/Sources/QuartzCore/QuartzCore-449.40.9/LayerKit/ogl/ogl-metal.mm, line 1005.
tid_403
0 libsystem_kernel.dylib 0x18d19e8e8 __ulock_wait + 8
1 libdispatch.dylib 0x18d06c0d8 _dispatch_ulock_wait + 48
2 libdispatch.dylib 0x18d06c200 _dispatch_thread_event_wait_slow + 36
3 libdispatch.dylib 0x18d069df8 _dispatch_barrier_sync_f_slow + 236
4 QuartzCore 0x1913e7090 CABackingStoreGetFrontTexture(CABackingStore*) + 92
5 QuartzCore 0x1913e7118 CABackingStorePrepareFrontTexture + 64
6 QuartzCore 0x1914db0a4 CA::Layer::prepare_commit(CA::Transaction*) + 320
7 QuartzCore 0x1914577f8 CA::Context::commit_transaction(CA::Transaction*) + 264
8 QuartzCore 0x19147ec58 CA::Transaction::commit() + 512
9 QuartzCore 0x19147f678 CA::Transaction::observer_callback(__CFRunLoopObserver*, unsigned long, void*) + 120
10 CoreFoundation 0x18e17b7dc __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 32
11 CoreFoundation 0x18e17940c __CFRunLoopDoObservers + 372
12 CoreFoundation 0x18e17989c __CFRunLoopRun + 1024
13 CoreFoundation 0x18e0a8048 CFRunLoopRunSpecific + 444
14 GraphicsServices 0x18fb2e198 GSEventRunModal + 180
15 UIKit 0x1940942fc -[UIApplication _run] + 684
16 UIKit 0x19408f034 UIApplicationMain + 208
17 NDC2010 0x100a321d4 wrapper_managed_to_native_UIKit_UIApplication_UIApplicationMain_int_string___intptr_intptr (<unknown>:1)
18 NDC2010 0x1009ae138 Xamarin_iOS_UIKit_UIApplication_Main_string___string_string (UIApplication.cs:63)
19 NDC2010 0x100526288 NDC2010_NDC2010_NDC2010Application_Main_string__ + 28620
20 NDC2010 0x100921ba4 wrapper_runtime_invoke_object_runtime_invoke_dynamic_intptr_intptr_intptr_intptr + 4204776
21 Mono 0x1019aa4e8 mono_jit_runtime_invoke + 1772
22 Mono 0x101a1ad64 do_runtime_invoke + 112
23 Mono 0x101a1d348 mono_runtime_exec_main + 832
24 Mono 0x101a1cf64 mono_runtime_run_main + 764
25 Mono 0x10198eb04 mono_jit_exec + 236
26 NDC2010 0x10051ed3c xamarin_main (monotouch-main.m:487)
27 NDC2010 0x101291970 main (main.arm64.m:133)
28 libdispatch.dylib 0x18d08c5b8 (Missing)
My app kept crashing with the same log, what fixed for me was a quick reset of device, i traced it to webView usage. I cant reset device every time so further testing revealed that i was using xcode 7.3 to build for ios10 that was the problem, after updating to xcode 8 and rebuilding the app i no longer get this crash. Hope this helps

Does Mac OS call display methods such as drawRect: concurrently from different threads? Isn't that dangerous when accessing the data model?

We have a subclass of NSTableRowView that overwrites drawSelectionInRect: (which is internally called by drawRect:). This method needs to access the NSManagedObjectContext, so as a sanity check we have an assertion there that we are in the main thread. Now it turns out that sometimes Apple calls drawRect from a non-main-thread (example stack trace below). Does this mean it could even do that concurrently from two different threads? I.e. we have to take care of thread safety ourselves when overwriting drawRect: and using the data model?
ERROR: Assertion failed: [NSThread isMainThread]: (ZS_AppDelegate.m:1287)
(
0 tomedo_kunden 0x00000001008af46a -[ZS_AppDelegate loggedInUser] + 554
1 tomedo_kunden 0x00000001016feca7 +[Nutzer loggedInUser] + 71
2 tomedo_kunden 0x0000000100f33397 +[ZSUserDefaults(MacOS) colorFromPreferences:] + 167
3 tomedo_kunden 0x00000001003d8265 -[Besuch(BesuchCategory) baseTextColor] + 101
4 tomedo_kunden 0x000000010071f846 -[ZSTableRowView drawSelectionInRect:] + 806
5 AppKit 0x00007fffd189d26c -[NSTableRowView drawRect:] + 242
6 AppKit 0x00007fffd184eba3 -[NSView(NSInternal) _recursive:displayRectIgnoringOpacity:inGraphicsContext:CGContext:topView:shouldChangeFontReferenceColor:] + 1318
7 AppKit 0x00007fffd184f053 -[NSView(NSInternal) _recursive:displayRectIgnoringOpacity:inGraphicsContext:CGContext:topView:shouldChangeFontReferenceColor:] + 2518
8 AppKit 0x00007fffd184e548 __46-[NSView(NSLayerKitGlue) drawLayer:inContext:]_block_invoke + 267
9 AppKit 0x00007fffd184e071 -[NSView(NSLayerKitGlue) _drawViewBackingLayer:inContext:drawingHandler:] + 1589
10 AppKit 0x00007fffd184da36 -[NSView(NSLayerKitGlue) drawLayer:inContext:] + 80
11 AppKit 0x00007fffd19839ff -[_NSBackingLayerContents drawLayer:inContext:] + 162
12 QuartzCore 0x00007fffd96a1e42 -[CALayer drawInContext:] + 257
13 AppKit 0x00007fffd19834d8 -[_NSTiledLayer drawTile:inContext:] + 624
14 AppKit 0x00007fffd198320e -[_NSTiledLayerContents drawLayer:inContext:] + 176
15 QuartzCore 0x00007fffd96a1e42 -[CALayer drawInContext:] + 257
16 AppKit 0x00007fffd1983155 -[NSTileLayer drawInContext:] + 169
17 QuartzCore 0x00007fffd9584a38 CABackingStoreUpdate_ + 3740
18 QuartzCore 0x00007fffd96a1a3c ___ZN2CA5Layer8display_Ev_block_invoke + 75
19 QuartzCore 0x00007fffd96a169d _ZN2CA5Layer8display_Ev + 1803
20 AppKit 0x00007fffd198306c -[NSTileLayer display] + 119
21 QuartzCore 0x00007fffd9695546 _ZN2CA5Layer17display_if_neededEPNS_11TransactionE + 572
22 QuartzCore 0x00007fffd9695671 _ZN2CA5Layer28layout_and_display_if_neededEPNS_11TransactionE + 35
23 QuartzCore 0x00007fffd968ae88 _ZN2CA7Context18commit_transactionEPNS_11TransactionE + 280
24 QuartzCore 0x00007fffd9581d55 _ZN2CA11Transaction6commitEv + 475
25 AppKit 0x00007fffd19701d9 __58-[_NSScrollingConcurrentVBLMonitor _updateScrollAnimation]_block_invoke + 972
26 AppKit 0x00007fffd196aa3a -[_NSScrollingConcurrentSharedData threadSafePropertyAccess:] + 44
27 AppKit 0x00007fffd196d127 -[_NSScrollingConcurrentVBLMonitor _updateScrollAnimation] + 672
28 AppKit 0x00007fffd196c84e -[_NSScrollingConcurrentVBLMonitor _synchronizeForVBLSerialNumber:timestamp:updateDuration:] + 561
29 AppKit 0x00007fffd196c5ad __42-[_NSScrollingConcurrentVBLMonitor resume]_block_invoke + 218
30 AppKit 0x00007fffd196c4ca __45-[NSScreen(NSScreenUpdate) addUpdateHandler:]_block_invoke_2 + 212
31 libdispatch.dylib 0x000000010345ffcc _dispatch_client_callout + 8
32 libdispatch.dylib 0x0000000103476bca _dispatch_continuation_pop + 1025
33 libdispatch.dylib 0x000000010346c6bc _dispatch_source_latch_and_call + 195
34 libdispatch.dylib 0x0000000103462e15 _dispatch_source_invoke + 1106
35 libdispatch.dylib 0x00000001034768f0 _dispatch_continuation_pop + 295
36 libdispatch.dylib 0x000000010346deda _dispatch_async_redirect_invoke + 777
37 libdispatch.dylib 0x0000000103462247 _dispatch_root_queue_drain + 671
38 libdispatch.dylib 0x0000000103461f58 _dispatch_worker_thread3 + 114
39 libsystem_pthread.dylib 0x00000001034d78c2 _pthread_wqthread + 1299
40 libsystem_pthread.dylib 0x00000001034d739d start_wqthread + 13
)
NSView subclasses can draw concurrently in recent releases of OS X. This behavior can be turned off by overriding canDrawConcurrently and returning NO.
You might find it preferable to separate the view from the model a little more and isolate the data to be rendered from the CoreData managed data a bit; pull the data to be rendered out into a local-only representation and let AppKit concurrently update the view.
https://developer.apple.com/reference/appkit/nsview/1483425-candrawconcurrently

What does this stack trace indicate? Crash caused by Xamarin.Media.MediaPicker.TakePhotoAsync on iOS8

What does this stack trace indicate? Crash caused by Xamarin.Media.MediaPicker.TakePhotoAsync on iOS8 on iPad2
I've logged a bug at...
https://bugzilla.xamarin.com/show_bug.cgi?id=22853
But I'd like to make sure that it is not something I'm doing. It works fine on iOS7.
OS Version: iOS 8.0 (12A365)
Report Version: 105
Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000002c
Triggered by Thread: 0
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x3ab05dfc __pthread_kill + 8
1 libsystem_pthread.dylib 0x3ab85d0e pthread_kill + 58
2 libsystem_c.dylib 0x3aaa5934 abort + 72
3 TouchContainer 0x00bd5b3a mono_handle_native_sigsegv (mini-exceptions.c:2360)
4 TouchContainer 0x00bdef72 mono_sigsegv_signal_handler (mini.c:6868)
5 libsystem_platform.dylib 0x3ab800a0 _sigtramp + 40
6 UIKit 0x30212304 _UIViewTopDownSubtreeTraversal + 260
7 UIKit 0x30212304 _UIViewTopDownSubtreeTraversal + 260
8 UIKit 0x305ab842 -[UIView(UIConstraintBasedLayout_EngineDelegate) _invalidateSystemLayoutSizeFittingSizeAtEngineDelegateLevel] + 118
9 UIKit 0x300429c0 -[UIView(AdditionalLayoutSupport) _setNeedsUpdateConstraintsNeedingLayout:] + 68
10 UIKit 0x305aa4e2 -[UIView(AdditionalLayoutSupport) _setSubviewWantsAutolayoutTripWantsAutolayout:] + 206
11 UIKit 0x2ff88588 -[UIView(Internal) _addSubview:positioned:relativeTo:] + 1352
12 UIKit 0x2ff88032 -[UIView(Hierarchy) addSubview:] + 26
13 UIKit 0x3024b2a2 __56-[UIPresentationController _transplantView:toSuperview:]_block_invoke + 242
14 UIKit 0x3024af8c -[UIPresentationController _performBlockWithoutTriggeringResponderEvents:] + 96
15 UIKit 0x3024b1a6 -[UIPresentationController _transplantView:toSuperview:] + 78
16 UIKit 0x3024e474 __71-[UIPresentationController _initViewHierarchyForPresentationSuperview:]_block_invoke + 768
17 UIKit 0x3024d358 __56-[UIPresentationController runTransitionForCurrentState]_block_invoke + 148
18 UIKit 0x2fffb916 _applyBlockToCFArrayCopiedToStack + 306
19 UIKit 0x2ff777da _afterCACommitHandler + 454
20 CoreFoundation 0x2caca842 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 18
21 CoreFoundation 0x2cac7f24 __CFRunLoopDoObservers + 272
22 CoreFoundation 0x2cac8326 __CFRunLoopRun + 910
23 CoreFoundation 0x2ca15dac CFRunLoopRunSpecific + 472
24 CoreFoundation 0x2ca15bbe CFRunLoopRunInMode + 102
25 GraphicsServices 0x33d4904c GSEventRunModal + 132
26 UIKit 0x2ffe0efc UIApplicationMain + 1436
27 TouchContainer 0x001d81ec wrapper_managed_to_native_MonoTouch_UIKit_UIApplication_UIApplicationMain_int_string___intptr_intptr + 268
28 TouchContainer 0x0018533c MonoTouch_UIKit_UIApplication_Main_string___intptr_intptr (UIApplication.cs:122)
29 TouchContainer 0x001852fc MonoTouch_UIKit_UIApplication_Main_string___string_string (UIApplication.cs:88)
30 TouchContainer 0x000ad800 Touch_Container_Application_Main_string__ (MainClass.cs:84)
31 TouchContainer 0x0036e9b4 wrapper_runtime_invoke_object_runtime_invoke_dynamic_intptr_intptr_intptr_intptr + 196
32 TouchContainer 0x00be115c mono_jit_runtime_invoke (mini.c:6730)
33 TouchContainer 0x00c2059a mono_runtime_invoke (object.c:2831)
34 TouchContainer 0x00c242a2 mono_runtime_exec_main (object.c:4088)
35 TouchContainer 0x00c240ea mono_runtime_run_main (object.c:3714)
36 TouchContainer 0x00bcea74 mono_jit_exec (driver.g.c:1009)
37 TouchContainer 0x00c59894 monotouch_main (monotouch-main.m:469)
38 TouchContainer 0x00bb0da0 main (main.armv7.m:65)
39 TouchContainer 0x000a9024 start + 36
It seems that what I was doing wrong was calling TakePhotoAsync from the Clicked event of an ActionSheet. The action sheet was still presented when the photo picker was presented. Pre iOS8 there must have been defensive code to silently work in this apparently illegal situation. The solution was to run the TakePhotoAsync in a BeginInvokeOnMainThread call. This queues the call on the main thread and allows the ActionSheet some space to finish closing.

wsdl2objc is not working with iphone SDK 4.2

We had a project using wsdl2objc to generate webclient for iphone application. The app was working fine with SDK 3.2, till lately we tried to test it with the new Xcode (SDK 4.2) and it throws strange EXC_BAD_ACCESS directly after sending an asynchronous request and surely never getting a response. Here is the stack trace:
0 libsystem_c.dylib 0x3452a200 OSAtomicAdd32 + 0
1 Foundation 0x30c317a4 -[NSOperation release] + 24
2 CoreFoundation 0x343df19a CFRelease + 62
3 CoreFoundation 0x343e1eb4 _CFAutoreleasePoolPop + 140
4 Foundation 0x30c211c4 -[NSAutoreleasePool release] + 92
5 UIKit 0x34b70f08 _UIApplicationHandleEvent + 5784
6 GraphicsServices 0x31884e70 PurpleEventCallback + 660
7 CoreFoundation 0x34451a90 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 20
8 CoreFoundation 0x34453838 __CFRunLoopDoSource1 + 160
9 CoreFoundation 0x34454606 __CFRunLoopRun + 514
10 CoreFoundation 0x343e4ebc CFRunLoopRunSpecific + 224
11 CoreFoundation 0x343e4dc4 CFRunLoopRunInMode + 52
12 GraphicsServices 0x31884418 GSEventRunModal + 108
13 GraphicsServices 0x318844c4 GSEventRun + 56
14 UIKit 0x34b9bd62 -[UIApplication _run] + 398
15 UIKit 0x34b99800 UIApplicationMain + 664
16 FFMobile 0x00002ed4 0x1000 + 7892
17 FFMobile 0x00002e88 0x1000 + 7816
I know it has to be something about releasing NSOperation. But I could not go any further. Does anybody know if the NSOperation is changed since SDK 4.0? Did anybody successfully test wsdl2objc with SDK 4.0?
EDIT: The WSDL that I use is here.

Resources