Date/Time: 2022-06-10 06:57:07.9651 +0800
Launch Time: 2022-06-09 17:42:25.7993 +0800
OS Version: iPhone OS 16.0 (20A5283p)
Release Type: Beta
Baseband Version: 2.04.00
Report Version: 104
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000058
Exception Codes: 0x0000000000000001, 0x0000000000000058
VM Region Info: 0x58 is not in any region. Bytes before following region: 206997290920
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
commpage (reserved) 3032000000-7000000000 [255.2G] ---/--- SM=NUL ...(unallocated)
Termination Reason: SIGNAL 11 Segmentation fault: 11
Terminating Process: exc handler [7705]
Triggered by Thread: 53
Thread 53 name:
Thread 53 Crashed:
0 libdispatch.dylib 0x0000000186f68554 dispatch_source_set_timer + 32 (source.c:1389)
1 PrivacyAccounting 0x000000020f05632c -[PACoalescingIntervalTracker coalesce:] + 420 (PACoalescingIntervalTracker.m:101)
2 PrivacyAccounting 0x000000020f04af30 __22-[PAAccessLogger log:]_block_invoke + 360 (PAAccessLogger.m:209)
3 libdispatch.dylib 0x0000000186f621cc _dispatch_block_async_invoke2 + 148 (queue.c:555)
4 libdispatch.dylib 0x0000000186f530f4 _dispatch_client_callout + 20 (object.m:560)
5 libdispatch.dylib 0x0000000186f5a7ac _dispatch_lane_serial_drain + 672 (inline_internal.h:2631)
6 libdispatch.dylib 0x0000000186f5b32c _dispatch_lane_invoke + 436 (queue.c:3939)
7 libdispatch.dylib 0x0000000186f65ebc _dispatch_workloop_worker_thread + 652 (queue.c:6766)
8 libsystem_pthread.dylib 0x00000001fe9190a8 _pthread_wqthread + 288 (pthread.c:2599)
9 libsystem_pthread.dylib 0x00000001fe918e48 start_wqthread + 8
ZhangHu
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
The problem background
Since the release of iOS 16.0 beta, we have been receiving a series of crash logs of our App, all of which occurred on iOS 16.0 beta, including:
iOS 16.0 Beta4 (20A5328h)
iOS 16.0 Beta3 (20A5312j)
iOS 16.0 Beta3 (20A5312g)
iOS 16.0 beta2 (20A5303i)
iOS 16.0 Beta1 (20A5283p)
Other than these system versions, it has not yet happened on any other iOS version. We suspect this issue has to do with the internal logic of the iOS 16.0 beta.
Common characteristics of the crash
This only happens in beta versions of iOS 16.0
Exception information is the same:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000058
Exception Codes: 0x0000000000000001, 0x0000000000000058
VM Region Info: 0x58 is not in any region. Bytes before following region: 206997290920
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
commpage (reserved) 3032000000-7000000000 [255.2G] ---/--- SM=NUL ...(unallocated)
Termination Reason: SIGNAL 11 Segmentation fault: 11
Terminating Process: exc handler [7705]
The top of the call stack for the crashed thread is all these frames:
0 libdispatch.dylib 0x0000000186f68554 dispatch_source_set_timer + 32 (source.c:1389)
1 PrivacyAccounting 0x000000020f05632c -[PACoalescingIntervalTracker coalesce:] + 420 (PACoalescingIntervalTracker.m:101)
2 PrivacyAccounting 0x000000020f04af30 __22-[PAAccessLogger log:]_block_invoke + 360 (PAAccessLogger.m:209)
Reproduction
We've been trying and analyzing these crash logs continuously since we received them, but we haven't found a way to reproduce them, and we haven't found suspectable codes.
Expectation
We are urgently and sincerely seeking Apple's help. We would like to know:
How can we developers avoid this crash?
Is Apple aware of this issue and will fix it in the subsequent release of iOS 16.0?
Crash log
2022-06-10_06-57-07.9651_3494.crash