gpt4 book ai didi

ios - Crashlytics 日志记录的循环问题?

转载 作者:行者123 更新时间:2023-11-29 11:29:05 25 4
gpt4 key购买 nike

我的 Swift 应用程序被 iOS (0x8badf00d) 杀死,看起来 Crashlytics 是罪魁祸首。这是崩溃报告的一部分——我假设它是 Crashlytics,因为代码上有 CLS 前缀。

Exception Type:  EXC_CRASH (SIGKILL)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace SPRINGBOARD, Code 0x8badf00d
Termination Description: SPRINGBOARD, scene-create watchdog transgression: com.rsginc.rmove exhausted CPU time allowance of 4.70 seconds | ProcessVisibility: Background | ProcessState: Running | WatchdogEvent: scene-create | WatchdogVisibility: Background | WatchdogCPUStatistics: ( | "Elapsed total CPU time (seconds): 7.550 (user 7.550, system 0.000), 10% CPU", | "Elapsed application CPU time (seconds): 5.119, 7% CPU" | )
Triggered by Thread: 0

Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libsystem_kernel.dylib 0x00000001fab7d948 write + 8
1 rMove 0x00000001048e6814 CLSSDKFileLog + 336
2 rMove 0x00000001048f2128 __CLSFileWriteWithRetries_block_invoke + 128
3 rMove 0x00000001048f203c CLSFileLoopWithWriteBlock + 56
4 rMove 0x00000001048f23ac CLSFileFDWriteUInt64 + 128
5 rMove 0x00000001048f248c CLSFileFDWriteInt64 + 116
6 rMove 0x00000001048e6804 CLSSDKFileLog + 320
7 rMove 0x00000001048f2128 __CLSFileWriteWithRetries_block_invoke + 128
8 rMove 0x00000001048f203c CLSFileLoopWithWriteBlock + 56
9 rMove 0x00000001048f23ac CLSFileFDWriteUInt64 + 128
10 rMove 0x00000001048f248c CLSFileFDWriteInt64 + 116
11 rMove 0x00000001048e6804 CLSSDKFileLog + 320
12 rMove 0x00000001048f2128 __CLSFileWriteWithRetries_block_invoke + 128
13 rMove 0x00000001048f203c CLSFileLoopWithWriteBlock + 56
14 rMove 0x00000001048f23ac CLSFileFDWriteUInt64 + 128
15 rMove 0x00000001048f248c CLSFileFDWriteInt64 + 116
...

该跟踪中的 5 行重复行重复了 102 次 - 我将其截断以考虑 StackOverflow 字符限制和可读性。

我没能找到其他人遇到这个问题 - 这是一个已知错误,还是我在 Crashlytics 调用中可能做错了什么?

最佳答案

我假设您的应用启动时间超过 20 秒。看看 documentation并找到代码为 0x8badf00d 的零件。

The exception code 0x8badf00d indicates that an application has been terminated by iOS because a watchdog timeout occurred. The application took too long to launch, terminate, or respond to system events. One common cause of this is doing synchronous networking on the main thread. Whatever operation is on Thread 0 needs to be moved to a background thread, or processed differently, so that it does not block the main thread.

关于ios - Crashlytics 日志记录的循环问题?,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/55461415/

25 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com