简体   繁体   English

由于看门狗,我的应用程序从后台返回时崩溃

[英]my app crash when it return from background because of watchdog

Exception Type: EXC_CRASH (SIGKILL) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Termination Reason: Namespace SPRINGBOARD, Code 0x8badf00d Termination Description: SPRINGBOARD, scene-update watchdog transgression: application< cbundlename >:354 exhausted real (wall clock) time allowance of 10.00 seconds |异常类型:EXC_CRASH (SIGKILL) 异常代码:0x0000000000000000, 0x0000000000000000 异常说明:EXC_CORPSE_NOTIFY 终止原因:命名空间 SPRINGBOARD,代码 0x8badf00d 终止说明:SPRINGBOARD,场景更新看门狗越界:应用程序< cbundlename时间耗尽>:354 10.00 秒 | ProcessVisibility: Foreground | ProcessVisibility:前景 | ProcessState: Running |进程状态:正在运行 | WatchdogEvent: scene-update | WatchdogEvent: 场景更新 | WatchdogVisibility: Background | WatchdogVisibility: 背景 | WatchdogCPUStatistics: ( | "Elapsed total CPU time (seconds): 9.630 (user 9.630, system 0.000), 6% CPU", | "Elapsed application CPU time (seconds): 1.088, 1% CPU" | ) Triggered by Thread: 0 WatchdogCPUStatistics: ( | "Elapsed total CPU time (seconds): 9.630 (user 9.630, system 0.000), 6% CPU", | "Elapsed application CPU time (seconds): 1.088, 1% CPU" | ) Triggered by Thread: 0

this is happening sometime to CLIENT, I almost can't reproduce this and I do not get any crashes neither in Xcode organiser nor in Crashlytics这有时会发生在客户身上,我几乎无法重现这一点,而且我在 Xcode 组织者和 Crashlytics 中都没有遇到任何崩溃
I can just get the logs from the device -> setting-> privacy-> analytics I have worked very hard to remove all memory leaks and to clean the main thread as I can move the task to DispatchQueue.background also, I have cleaned logic from AppDelegate functions and it still happens.我可以从设备获取日志-> 设置-> 隐私-> 分析我已经非常努力地删除所有 memory 泄漏并清理主线程,因为我也可以将任务移动到DispatchQueue.background ,我已经清理了逻辑来自AppDelegate函数,它仍然会发生。

Please advise!请指教!

Code 0x8badf00d is the error code that the watchdog raises when an application takes too long to launch or terminate.代码 0x8badf00d 是当应用程序启动或终止时间过长时看门狗引发的错误代码。

Usually, it means you either have an infinite loop somewhere, or you are waiting for network IO on the main thread.通常,这意味着您在某处有一个无限循环,或者您正在主线程上等待网络 IO。 There's also the possibility that the user is force-quitting the application.用户也有可能强制退出应用程序。

You can refer https://developer.apple.com/library/archive/qa/qa1693/_index.html apple's reference document for more details and the possible ways to handle this scenario in your project.您可以参考https://developer.apple.com/library/archive/qa/qa1693/_index.html Apple 的参考文档以获取更多详细信息以及在您的项目中处理此场景的可能方法。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 iOS 应用程序被 WatchDog 崩溃,但在从 Xcode 运行时可以正常工作 - iOS app crashes by WatchDog but works when running from Xcode 由于SIGABRT,应用程式当机 - App crash because of SIGABRT 由于超时返回dispatch_group_wait()时,iOS 8崩溃 - Crash on iOS 8 when dispatch_group_wait() return because of timeout 当应用进入后台时,GCDWebServer崩溃 - Crash in GCDWebServer when app enters background 应用程序进入前台时崩溃-因为委托=自我? - Crash when app enters foreground - because delegate = self? 前景iPhone应用程序导致我的后台应用程序崩溃 - foreground iphone app causing my background app to crash 在iOS上从后台返回到应用 - Return to app from background on iOS 我的应用崩溃,原因是&#39;UITableView dataSource必须从tableView:cellForRowAtIndexPath返回一个单元格 - My app crash, reason 'UITableView dataSource must return a cell from tableView:cellForRowAtIndexPath 当应用程序在后台接收推送通知时,应用程序崩溃 - When App in Background and receiving push notification tap App goes crash 由于内存问题在后台线程上加载SpriteKit场景导致应用程序崩溃 - Loading SpriteKit scene on background thread causes app to crash because of memory issues
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM