I just added AdMob into my UIViewController, and when I run the app, it freezes for a few seconds, and then this shows up:
=================================================================
Main Thread Checker: UI API called on a background thread: -[UIApplication applicationState]
PID: 8093, TID: 1911410, Thread name: com.apple.CoreMotion.MotionThread, Queue name: com.apple.root.default-qos.overcommit, QoS: 0
Backtrace:
4 libobjc.A.dylib 0x0000000198a9b894 <redacted> + 56
5 CoreMotion 0x000000019f321040 CoreMotion + 307264
6 CoreMotion 0x000000019f321574 CoreMotion + 308596
7 CoreMotion 0x000000019f321484 CoreMotion + 308356
8 CoreMotion 0x000000019f352c64 CoreMotion + 511076
9 CoreMotion 0x000000019f352cc4 CoreMotion + 511172
10 CoreFoundation 0x00000001998324fc <redacted> + 28
11 CoreFoundation 0x0000000199831de0 <redacted> + 276
12 CoreFoundation 0x000000019982d0e4 <redacted> + 2324
13 CoreFoundation 0x000000019982c4b8 CFRunLoopRunSpecific + 452
14 CoreFoundation 0x000000019982d21c CFRunLoopRun + 84
15 CoreMotion 0x000000019f3525fc CoreMotion + 509436
16 libsystem_pthread.dylib 0x00000001994a7974 <redacted> + 132
17 libsystem_pthread.dylib 0x00000001994a78d0 _pthread_start + 52
18 libsystem_pthread.dylib 0x00000001994afddc thread_start + 4
Any tips?
Your problem is this process is in the Main Thread . Main Thread for only UI action. Otherwise UI will freeze.
You should do it in background thread.
DispatchQueue.global(qos: .background).async {
// Your code
}
Enjoy.
Related
I'm getting this error everytime my app starts :
Main Thread Checker: UI API called on a background thread: -[UIApplication statusBarOrientation]
PID: 5264, TID: 1948690, Thread name: (none), Queue name: NSOperationQueue 0x107c31d80 (QOS: UNSPECIFIED), QoS: 0
Backtrace:
4 app 0x0000000104debcf4 -[FIRCLSReportManager captureInitialNotificationStates] + 144
5 app 0x0000000104deba88 -[FIRCLSReportManager setupStateNotifications] + 44
6 app 0x0000000104de9478 -[FIRCLSReportManager startCrashReporterWithProfilingMark:report:] + 256
7 app 0x0000000104de8210 -[FIRCLSReportManager startWithProfilingMark:] + 1188
8 app 0x0000000104e01be4 -[FIRCrashlytics initWithApp:appInfo:installations:analytics:] + 1448
9 app 0x0000000104e022e8 __38+[FIRCrashlytics componentsToRegister]_block_invoke + 532
10 app 0x0000000104daf8bc -[FIRComponentContainer instantiateInstanceForProtocol:withBlock:] + 132
11 app 0x0000000104dafb60 -[FIRComponentContainer instanceForProtocol:] + 344
12 app 0x0000000104db0234 +[FIRComponentType instanceForProtocol:inContainer:] + 104
13 app 0x0000000104e023d8 +[FIRCrashlytics crashlytics] + 136
14 app 0x0000000104923488 -[CrashReportingManager logWithFormat:arguments:] + 136
15 app 0x00000001049233e8 -[CrashReportingManager logWithFormat:] + 84
16 app 0x00000001049d6e4c __49-[AccountManager clearTempDataStorageCompletion:]_block_invoke + 636
17 Foundation 0x00000001b04a33a0 7B1733B1-74C9-3A33-8A58-853B0A029826 + 1131424
18 Foundation 0x00000001b03ad0c8 7B1733B1-74C9-3A33-8A58-853B0A029826 + 123080
19 Foundation 0x00000001b04a5628 7B1733B1-74C9-3A33-8A58-853B0A029826 + 1140264
20 Foundation 0x00000001b03acd60 7B1733B1-74C9-3A33-8A58-853B0A029826 + 122208
21 Foundation 0x00000001b04a6020 7B1733B1-74C9-3A33-8A58-853B0A029826 + 1142816
22 Foundation 0x00000001b04a5aec 7B1733B1-74C9-3A33-8A58-853B0A029826 + 1141484
23 libdispatch.dylib 0x0000000107a8d268 _dispatch_block_async_invoke2 + 104
24 libdispatch.dylib 0x0000000107a7ebd8 _dispatch_client_callout + 16
25 libdispatch.dylib 0x0000000107a817dc _dispatch_continuation_pop + 524
26 libdispatch.dylib 0x0000000107a80c5c _dispatch_async_redirect_invoke + 624
27 libdispatch.dylib 0x0000000107a90160 _dispatch_root_queue_drain + 376
28 libdispatch.dylib 0x0000000107a90a88 _dispatch_worker_thread2 + 156
29 libsystem_pthread.dylib 0x00000001afdfab48 _pthread_wqthread + 212
30 libsystem_pthread.dylib 0x00000001afdfd760 start_wqthread + 8
It seems Firebase is calling statusBarOrientation on a background thread ?
Is anyone else getting this or knows how to fix this ?
You are trying to access +[FIRCrashlytics crashlytics] on a non-main thread.
EDIT: This appears to be resolved on iOS 13. Leaving all the original details below.
I'm getting a crash when instantiating my CMMotionManager object for Core Motion. This is on an iPhone Xs running iOS 12.0.1.
I can reliably reproduce this with a single-view app, with the following view controller.
import UIKit
import CoreMotion
class ViewController: UIViewController {
var motion: CMMotionManager?
override func viewDidLoad() {
super.viewDidLoad()
// This causes a crash on iPhone Xs, iOS 12.0.1
self.motion = CMMotionManager()
}
}
Full sample project is at https://github.com/doctorcolinsmith/motiontestcrash/tree/master
When running the above, I am getting a fault on a thread with the following output in the debugger.
=================================================================
Main Thread Checker: UI API called on a background thread: -[UIApplication applicationState]
PID: 3634, TID: 630341, Thread name: com.apple.CoreMotion.MotionThread, Queue name: com.apple.root.default-qos.overcommit, QoS: 0
Backtrace:
4 libobjc.A.dylib 0x000000019b0d3894 <redacted> + 56
5 CoreMotion 0x00000001a19337a4 CoreMotion + 305060
6 CoreMotion 0x00000001a1933cd8 CoreMotion + 306392
7 CoreMotion 0x00000001a1933be8 CoreMotion + 306152
8 CoreMotion 0x00000001a19653cc CoreMotion + 508876
9 CoreMotion 0x00000001a196542c CoreMotion + 508972
10 CoreFoundation 0x000000019be6c888 <redacted> + 28
11 CoreFoundation 0x000000019be6c16c <redacted> + 276
12 CoreFoundation 0x000000019be67470 <redacted> + 2324
13 CoreFoundation 0x000000019be66844 CFRunLoopRunSpecific + 452
14 CoreFoundation 0x000000019be675a8 CFRunLoopRun + 84
15 CoreMotion 0x00000001a1964d64 CoreMotion + 507236
16 libsystem_pthread.dylib 0x000000019bae1a04 <redacted> + 132
17 libsystem_pthread.dylib 0x000000019bae1960 _pthread_start + 52
18 libsystem_pthread.dylib 0x000000019bae9df4 thread_start + 4
2018-10-24 16:19:31.423680-0700 motiontest[3634:630341] [reports] Main Thread Checker: UI API called on a background thread: -[UIApplication applicationState]
PID: 3634, TID: 630341, Thread name: com.apple.CoreMotion.MotionThread, Queue name: com.apple.root.default-qos.overcommit, QoS: 0
Backtrace:
4 libobjc.A.dylib 0x000000019b0d3894 <redacted> + 56
5 CoreMotion 0x00000001a19337a4 CoreMotion + 305060
6 CoreMotion 0x00000001a1933cd8 CoreMotion + 306392
7 CoreMotion 0x00000001a1933be8 CoreMotion + 306152
8 CoreMotion 0x00000001a19653cc CoreMotion + 508876
9 CoreMotion 0x00000001a196542c CoreMotion + 508972
10 CoreFoundation 0x000000019be6c888 <redacted> + 28
11 CoreFoundation 0x000000019be6c16c <redacted> + 276
12 CoreFoundation 0x000000019be67470 <redacted> + 2324
13 CoreFoundation 0x000000019be66844 CFRunLoopRunSpecific + 452
14 CoreFoundation 0x000000019be675a8 CFRunLoopRun + 84
15 CoreMotion 0x00000001a1964d64 CoreMotion + 507236
16 libsystem_pthread.dylib 0x000000019bae1a04 <redacted> + 132
17 libsystem_pthread.dylib 0x000000019bae1960 _pthread_start + 52
18 libsystem_pthread.dylib 0x000000019bae9df4 thread_start + 4
(lldb)
Has anyone encountered this before or have an idea on how to solve the crash?
Well, I've tested your application both physical iPhone 6S and iPhone 7 - obviously with iOS 12.0.1. I've also checked for a couple of things in your project and couldn't reproduce your problem at all - not even in simulators - and I don't think it's possible to download a simulator with specific fixes (12.0.x), only with minor version updates - so 12.1 being the next one. This looks really specific on iPhone XS hardware, and I would suggest you to fill an issue with Apple support.
EDIT: Well, I saw that you've already filled a bug report on openradar. This guy even referenced the bug report status on openradar-mirror.
I don't know much about CoreMotion, but the error message tells you you're trying to call a UI action on a background thread. Try putting your code into:
DispatchQueue.main.async {
//your code here
}
It also seems you're trying to do UI related actions in viewDidLoad(). Technically that's fine, but remember that some views probably aren't layed out at that point in time.
I really dont know what happened to my app but since I've added the touchid function, app is slower then before and strange writings appear.
I've added a UiViewController before the main controller, so I can check there without show any data to the user until he logged success with touchid.
All right, on my iphone 6s also, but it is very very slow now and it has appeared this on my console after the success of the touchid function:
success!!!!
=================================================================
Main Thread Checker: UI API called on a background thread: -[UIView bounds]
PID: 8460, TID: 1642991, Thread name: (none), Queue name: com.apple.root.default-qos, QoS: 21
Backtrace:
4 LAMer 0x000000010c035d96 _T0So16UIViewControllerC5LAMerE14displaySpinnerSo0A0CAF6onView_tFZ + 54
5 LAMer 0x000000010c060a85 _T05LAMer18AuthViewControllerC13viewDidAppearySbFySbcfU_ + 245
6 LAMer 0x000000010c060e4e _T05LAMer18AuthViewControllerC13viewDidAppearySbFySbcfU_TA + 62
7 LAMer 0x000000010c0374d0 _T0So16UIViewControllerC5LAMerE25authenticationWithTouchIDyySbc10completion_tFySb_s5Error_pSgtcfU_ + 336
8 LAMer 0x000000010c037c2c _T0So16UIViewControllerC5LAMerE25authenticationWithTouchIDyySbc10completion_tFySb_s5Error_pSgtcfU_TA + 108
9 LAMer 0x000000010c037cb3 _T0Sbs5Error_pSgIxyx_SbSo7NSErrorCSgIyByy_TR + 115
10 LocalAuthentication 0x000000010f42edf6 __50-[LAContext evaluatePolicy:localizedReason:reply:]_block_invoke_2 + 72
11 LocalAuthentication 0x000000010f42e2a9 __42-[LAContext evaluatePolicy:options:reply:]_block_invoke_2 + 615
12 LocalAuthentication 0x000000010f4293df __52-[LAClient evaluatePolicy:options:uiDelegate:reply:]_block_invoke + 224
13 libdispatch.dylib 0x00000001124dc2f7 _dispatch_call_block_and_release + 12
14 libdispatch.dylib 0x00000001124dd33d _dispatch_client_callout + 8
15 libdispatch.dylib 0x00000001124e2251 _dispatch_queue_override_invoke + 1458
16 libdispatch.dylib 0x00000001124e9102 _dispatch_root_queue_drain + 772
17 libdispatch.dylib 0x00000001124e8da0 _dispatch_worker_thread3 + 132
18 libsystem_pthread.dylib 0x00000001129a81ca _pthread_wqthread + 1387
19 libsystem_pthread.dylib 0x00000001129a7c4d start_wqthread + 13
=================================================================
Main Thread Checker: UI API called on a background thread: -[UIView initWithFrame:]
PID: 8460, TID: 1642991, Thread name: (none), Queue name: com.apple.root.default-qos, QoS: 21
Backtrace:
4 LAMer 0x000000010c03802d _T0So6UIViewCABSC6CGRectV5frame_tcfcTO + 77
5 LAMer 0x000000010c036064 _T0So6UIViewCABSC6CGRectV5frame_tcfC + 100
6 LAMer 0x000000010c035db3 _T0So16UIViewControllerC5LAMerE14displaySpinnerSo0A0CAF6onView_tFZ + 83
7 LAMer 0x000000010c060a85 _T05LAMer18AuthViewControllerC13viewDidAppearySbFySbcfU_ + 245
8 LAMer 0x000000010c060e4e _T05LAMer18AuthViewControllerC13viewDidAppearySbFySbcfU_TA + 62
9 LAMer 0x000000010c0374d0 _T0So16UIViewControllerC5LAMerE25authenticationWithTouchIDyySbc10completion_tFySb_s5Error_pSgtcfU_ + 336
10 LAMer 0x000000010c037c2c _T0So16UIViewControllerC5LAMerE25authenticationWithTouchIDyySbc10completion_tFySb_s5Error_pSgtcfU_TA + 108
11 LAMer 0x000000010c037cb3 _T0Sbs5Error_pSgIxyx_SbSo7NSErrorCSgIyByy_TR + 115
12 LocalAuthentication 0x000000010f42edf6 __50-[LAContext evaluatePolicy:localizedReason:reply:]_block_invoke_2 + 72
13 LocalAuthentication 0x000000010f42e2a9 __42-[LAContext evaluatePolicy:options:reply:]_block_invoke_2 + 615
14 LocalAuthentication 0x000000010f4293df __52-[LAClient evaluatePolicy:options:uiDelegate:reply:]_block_invoke + 224
15 libdispatch.dylib 0x00000001124dc2f7 _dispatch_call_block_and_release + 12
16 libdispatch.dylib 0x00000001124dd33d _dispatch_client_callout + 8
17 libdispatch.dylib 0x00000001124e2251 _dispatch_queue_override_invoke + 1458
18 libdispatch.dylib 0x00000001124e9102 _dispatch_root_queue_drain + 772
19 libdispatch.dylib 0x00000001124e8da0 _dispatch_worker_thread3 + 132
20 libsystem_pthread.dylib 0x00000001129a81ca _pthread_wqthread + 1387
21 libsystem_pthread.dylib 0x00000001129a7c4d start_wqthread + 13
After this, main controller appear and data of that controller correctly log into console.
Could I ask you what is this code above that appears in my console and if you are already know that touchid make app doing this stuff..
Thank you in advice
This doesn't look like a TouchID issue at all. You are performing UI actions on a background thread. You must call all UI on the main thread.
Look at recent changes to your code and see what you've changed.
Slowness and/or unresponsiveness is classic UI on a background thread issue.
See Main Thread Checker
Main Thread Checker: UI API called on a background thread: -[UIView setHidden:]
PID: 9947, TID: 1414260, Thread name: (none), Queue name: com.apple.root.default-qos.overcommit, QoS: 21
Backtrace:
4 doctor 0x0000000100d2e80f -[LoginController load:] + 3279
5 Foundation 0x00000001011ba8ac __NSThread__start__ + 1197
6 libsystem_pthread.dylib 0x0000000106ea16c1 _pthread_body + 340
7 libsystem_pthread.dylib 0x0000000106ea156d _pthread_body + 0
8 libsystem_pthread.dylib 0x0000000106ea0c5d thread_start + 13
2017-11-21 14:54:59.253674+0800 doctor[9947:1414260] [reports] Main Thread Checker: UI API called on a background thread: -[UIView setHidden:]
PID: 9947, TID: 1414260, Thread name: (none), Queue name: com.apple.root.default-qos.overcommit, QoS: 21
Backtrace:
4 doctor 0x0000000100d2e80f -[LoginController load:] + 3279
5 Foundation 0x00000001011ba8ac __NSThread__start__ + 1197
6 libsystem_pthread.dylib 0x0000000106ea16c1 _pthread_body + 340
7 libsystem_pthread.dylib 0x0000000106ea156d _pthread_body + 0
8 libsystem_pthread.dylib 0x0000000106ea0c5d thread_start + 13
2017-11-21 14:54:59.379571+0800 doctor[9947:1414260] This application is modifying the autolayout engine from a background thread after the engine was accessed from the main thread. This can lead to engine corruption and weird crashes.
Stack:(
0 Foundation 0x00000001013d5ec6 _AssertAutolayoutOnAllowedThreadsOnly + 77
1 Foundation 0x00000001011dfd7a -[NSISEngine withBehaviors:performModifications:] + 28
2 UIKit 0x000000010240d9fc __57-[UIView(AdditionalLayoutSupport) _switchToLayoutEngine:]_block_invoke + 604
3 UIKit 0x000000010240d778 -[UIView(AdditionalLayoutSupport) _switchToLayoutEngine:] + 223
4 UIKit 0x0000000101954125 __45-[UIView(Hierarchy) _postMovedFromSuperview:]_block_invoke + 112
5 UIKit 0x0000000101954033 -[UIView(Hierarchy) _postMovedFromSuperview:] + 828
6 UIKit 0x000000010196494d -[UIView(Internal) _addSubview:positioned:relativeTo:] + 1973
7 UIKit 0x0000000101ce3461 -[UILayoutContainerView addSubview:] + 75
8 UIKit 0x0000000101a76dee -[UINavigationController _unhideNavigationBarForEdge:] + 99
9 UIKit 0x0000000101a77098 -[UINavigationController _setNavigationBarHidden:edge:duration:] + 208
10 UIKit 0x0000000101a74b1e -[UINavigationController setNavigationBarHidden:animated:] + 141
11 doctor 0x0000000100d2e863 -[LoginController load:] + 3363
12 Foundation 0x00000001011ba8ac __NSThread__start__ + 1197
13 libsystem_pthread.dylib 0x0000000106ea16c1 _pthread_body + 340
14 libsystem_pthread.dylib 0x0000000106ea156d _pthread_body + 0
15 libsystem_pthread.dylib 0x0000000106ea0c5d thread_start + 13
)
especially
This application is modifying the autolayout engine from a background
thread after the engine was accessed from the main thread. This can
lead to engine corruption and weird crashes.
this tip repeats many times, until
2017-11-21 14:56:57.993852+0800 doctor[9947:1414234] Received XPC
error Connection interrupted for message type 3
kCFNetworkAgentXPCMessageTypePACQuery
2017-11-21 14:56:57.994722+0800 doctor[9947:1414234] Received XPC error
Connection invalid for message type 3
kCFNetworkAgentXPCMessageTypePACQuery
Then app crushes, has no response. And there isn't other error messages in the console. Any way to know the crush reason and how to solve it. Thanks!
Check your LoginController. There must be code like yourView.hidden = YES/NO.
Change that line of code to
dispatch_async(dispatch_get_main_queue(), ^{
//yourView.hidden = YES;
//or
//yourView.hidden = NO;
});
I used the code below to send mail:
MFMailComposeViewController *picker = [[MFMailComposeViewController alloc] init];
picker.mailComposeDelegate = self;
[picker setSubject:#"my title"];
NSMutableString *emailBody = [[NSMutableString alloc] initWithString: #"Hi\n\n"];
[emailBody appendString: #"test"];
[picker setMessageBody:emailBody isHTML:NO];
[self presentModalViewController:picker animated:YES];
[picker release];
[emailBody release];
The code works well on old OS version (Base SDK 5.0, Deployment Target 4.0). I just upgraded to Xcode 4.5 with iOS 6.0 as the Base SDK, Deployment Target still 4.3, and the code still works well on Simulator with 5.0, 5.1, and 6.0.
Now I installed the app to iPad with iOS 4.3.3. The MFMailComposeViewController does not appear, it hogs and the app stops working. I checked the device log, it displays:
Incident Identifier: 53CF815B-36FB-4523-8E58-03D80E6BD2D6
CrashReporter Key: e1ce74069fc4d91cdf244ef60282649f2ea4716e
Hardware Model: iPad1,1
Process: MyApp [1018]
Path: /var/mobile/Applications/75088803-4768-4CD6-A561-553F4A182229/MyApp.app/MyApp
Identifier: MyApp
Version: ??? (???)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2012-11-16 14:29:59.959 +0800
OS Version: iPhone OS 4.3.3 (8J3)
Report Version: 104
Exception Type: 00000020
Exception Codes: 0x8badf00d
Highlighted Thread: 0
Application Specific Information:
MyApp[1018] has active assertions beyond permitted time:
{(
<SBProcessAssertion: 0x1fa0dd00> identifier: Suspending process: MyApp[1018] permittedBackgroundDuration: 10.000000 reason: suspend owner pid:30 preventSuspend preventThrottleDownCPU preventThrottleDownUI
)}
Elapsed total CPU time (seconds): 0.770 (user 0.460, system 0.310), 8% CPU
Elapsed application CPU time (seconds): 0.000, 0% CPU
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0:
0 libsystem_kernel.dylib 0x332e5c00 mach_msg_trap + 20
1 libsystem_kernel.dylib 0x332e5758 mach_msg + 44
2 AppSupport 0x33bbb7b8 CPDMTwoWayMessage + 164
3 AppSupport 0x33bba530 -[CPDistributedMessagingCenter _sendMessage:userInfoData:oolKey:oolData:makeServer:receiveReply:nonBlocking:error:] + 352
4 AppSupport 0x33bba0b2 -[CPDistributedMessagingCenter _sendMessage:userInfo:receiveReply:error:toTarget:selector:context:nonBlocking:] + 618
5 AppSupport 0x33bb91ae -[CPDistributedMessagingCenter _sendMessage:userInfo:receiveReply:error:toTarget:selector:context:] + 58
6 AppSupport 0x33bb9312 -[CPDistributedMessagingCenter sendMessageAndReceiveReplyName:userInfo:] + 42
7 MessageUI 0x3693c1fa _CallMessageUIServiceMethod + 182
8 MessageUI 0x3693c01e +[MFMailAccountProxy reloadAccounts] + 22
9 MessageUI 0x3693bf6c +[MFMailComposeController _refreshMailAccountsIfNecessary] + 32
10 MessageUI 0x3693bf2a +[MFMailComposeController isSetupForDelivery] + 10
11 MessageUI 0x3693be80 +[MFMailComposeViewController canSendMail] + 24
12 MessageUI 0x3693bc36 -[MFMailComposeViewController initWithComposition:contentSize:mailComposeControllerOptions:] + 42
13 MessageUI 0x3693bbf8 -[MFMailComposeViewController initWithComposition:] + 28
14 MessageUI 0x36963fac -[MFMailComposeViewController initWithNibName:bundle:] + 44
15 UIKit 0x329e8a0c -[UIViewController init] + 12
16 MyApp 0x000d09ee 0xb5000 + 113134
17 MyApp 0x000e3820 0xb5000 + 190496
18 UIKit 0x32ad1036 -[UIActionSheet(Private) _buttonClicked:] + 186
19 CoreFoundation 0x32dc956a -[NSObject(NSObject) performSelector:withObject:withObject:] + 18
20 UIKit 0x329ceec2 -[UIApplication sendAction:to:from:forEvent:] + 78
21 UIKit 0x329cee62 -[UIApplication sendAction:toTarget:fromSender:forEvent:] + 26
22 UIKit 0x329cee34 -[UIControl sendAction:to:forEvent:] + 32
23 UIKit 0x329ceb86 -[UIControl(Internal) _sendActionsForEvents:withEvent:] + 350
24 UIKit 0x329cf41c -[UIControl touchesEnded:withEvent:] + 336
25 UIKit 0x329cdbee -[UIWindow _sendTouchesForEvent:] + 362
26 UIKit 0x329cd568 -[UIWindow sendEvent:] + 256
27 UIKit 0x329b630c -[UIApplication sendEvent:] + 292
28 UIKit 0x329b5c4c _UIApplicationHandleEvent + 5084
29 GraphicsServices 0x35c8ee70 PurpleEventCallback + 660
30 CoreFoundation 0x32e30a90 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 20
31 CoreFoundation 0x32e32838 __CFRunLoopDoSource1 + 160
32 CoreFoundation 0x32e33606 __CFRunLoopRun + 514
33 CoreFoundation 0x32dc3ebc CFRunLoopRunSpecific + 224
34 CoreFoundation 0x32dc3dc4 CFRunLoopRunInMode + 52
35 GraphicsServices 0x35c8e418 GSEventRunModal + 108
36 GraphicsServices 0x35c8e4c4 GSEventRun + 56
37 UIKit 0x329e0d62 -[UIApplication _run] + 398
38 UIKit 0x329de800 UIApplicationMain + 664
39 MyApp 0x000c95a4 0xb5000 + 83364
40 MyApp 0x000b73b8 0xb5000 + 9144
Thread 1 name: Dispatch queue: com.apple.libdispatch-manager
Thread 1:
0 libsystem_kernel.dylib 0x332e8fbc kevent + 24
1 libdispatch.dylib 0x33abc032 _dispatch_mgr_invoke + 706
2 libdispatch.dylib 0x33abd03a _dispatch_queue_invoke + 86
3 libdispatch.dylib 0x33abc5ea _dispatch_worker_thread2 + 186
4 libsystem_c.dylib 0x363d958a _pthread_wqthread + 258
5 libsystem_c.dylib 0x363d9bbc start_wqthread + 0
Thread 2 name: WebThread
Thread 2:
0 libsystem_kernel.dylib 0x332e5c00 mach_msg_trap + 20
1 libsystem_kernel.dylib 0x332e5758 mach_msg + 44
2 CoreFoundation 0x32e312b8 __CFRunLoopServiceMachPort + 88
3 CoreFoundation 0x32e33562 __CFRunLoopRun + 350
4 CoreFoundation 0x32dc3ebc CFRunLoopRunSpecific + 224
5 CoreFoundation 0x32dc3dc4 CFRunLoopRunInMode + 52
6 WebCore 0x31e5c27e RunWebThread(void*) + 382
7 libsystem_c.dylib 0x363d830a _pthread_start + 242
8 libsystem_c.dylib 0x363d9bb4 thread_start + 0
Any comment welcome.
The stack trace looks like this is not your fault, it’s system code that hangs and leads to your app being killed. There’s a post in the Developer Forums (non-public link, sorry) that suggest that this might be connected to the system Mail.app.
I’d try rebooting the device and similar tricks, but in the end your app might still be unstable on 4.3 in general. Do you really need to support 4.3?