Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2019.4
2020.1.15f1
2020.2
2021.1
2021.2
Issue ID
1295799
Regression
No
[iOS 14] EXC_BAD_ACCESS crash from com.apple.arkit.ardisplaylink
Steps to reproduce:
1. Download and open the attached "ARKitTest" project
2. Build and deploy the project to iOS
Reproduced with:2018.4.31f1, 2019.4.20f1, 2020.2.4f1, 2021.1.0b5, 2021.2.0a4
Reproducible with iPhone 12 Pro (iOS 14.2.1)
-
jbvobling
Jul 06, 2021 06:24
Also experiencing the same situation in 2020.3.8f1 LTS
-
leesungchul
Jun 22, 2021 04:42
same
I am on iOS version 14.6com.apple.arkit.ardisplaylink.0x2832f0840 (37): EXC_BAD_ACCESS (code=2, address=0x1590901710)
-
marnsmith
May 26, 2021 23:36
Related:
Thread 41 name: com.apple.arkit.ardisplaylink.0x2801f61c0
Thread 41 Crashed:
0 libobjc.A.dylib 0x00000001997af1e0 objc_msgSend + 32
1 CoreFoundation 0x0000000184c4a5e8 -[NSArray indexOfObject:inSortedRange:options:usingComparator:] + 380
2 ARKitCore 0x00000001b08c146c -[ARTimeKeyedList insertionIndexForTime:] + 96
3 ARKitCore 0x00000001b08c16a8 -[ARTimeKeyedList appendObject:forTime:] + 112
4 ARKitCore 0x00000001b083dbec -[ARWorldAlignmentTechnique processData:] + 188
5 ARKitCore 0x00000001b07fcfa8 -[ARParentTechnique processData:onTechniques:] + 220
6 ARKitCore 0x00000001b07fce8c -[ARParentTechnique processData:] + 92
7 ARKitCore 0x00000001b085833c __40-[ARSession sensor:didOutputSensorData:]_block_invoke_2 + 460
8 ARKitCore 0x00000001b082f2a4 -[ARRenderSyncScheduler _tryNextBlockWithTotalTried:] + 376
9 ARKitCore 0x00000001b082ec00 __57-[ARRenderSyncScheduler initWithExpectedFramesPerSecond:]_block_invoke + 40
10 ARKitCore 0x00000001b08626c0 __36-[ARDisplayLink displayLinkCallback]_block_invoke + 64
11 Foundation 0x000000018611c428 __NSFireTimer + 104
12 CoreFoundation 0x0000000184cd108c __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 32
13 CoreFoundation 0x0000000184cd0c88 __CFRunLoopDoTimer + 1076
14 CoreFoundation 0x0000000184cd00d8 __CFRunLoopDoTimers + 328
15 CoreFoundation 0x0000000184cc9e8c __CFRunLoopRun + 1944
16 CoreFoundation 0x0000000184cc91c0 CFRunLoopRunSpecific + 600
17 CoreFoundation 0x0000000184cca2ac CFRunLoopRun + 64
18 ARKitCore 0x00000001b07d50b0 -[ARRunLoop _startThread] + 584
19 Foundation 0x000000018611b2fc __NSThread__start__ + 864
20 libsystem_pthread.dylib 0x00000001d0770c00 _pthread_start + 320
21 libsystem_pthread.dylib 0x00000001d0779758 thread_start + 8 -
marnsmith
May 26, 2021 23:01
I'm getting this very frequently. iOS 14.5.1, Unity 2020.3.9f1 and 2021.1.3f1. Also using face + world tracking.
I see this is closed, but it's kind of a showstopper. Is there any other information e.g. from Apple, potential workarounds, timelines, etc?
Thread 41 name: com.apple.arkit.ardisplaylink.0x282d48800
Thread 41 Crashed:
0 libobjc.A.dylib 0x00000001997d2dd0 objc_release + 16
1 ARKitCore 0x00000001b087f7a8 -[ARDeviceOrientationData setDeviceMotion:] + 56
2 ARKitCore 0x00000001b08c0ecc -[ARDeviceOrientationSensor currentData] + 232
3 ARKitCore 0x00000001b08582f0 __40-[ARSession sensor:didOutputSensorData:]_block_invoke_2 + 384
4 ARKitCore 0x00000001b082f2a4 -[ARRenderSyncScheduler _tryNextBlockWithTotalTried:] + 376
5 ARKitCore 0x00000001b082ec00 __57-[ARRenderSyncScheduler initWithExpectedFramesPerSecond:]_block_invoke + 40
6 ARKitCore 0x00000001b08626c0 __36-[ARDisplayLink displayLinkCallback]_block_invoke + 64
7 Foundation 0x000000018611c428 __NSFireTimer + 104
8 CoreFoundation 0x0000000184cd108c __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 32
9 CoreFoundation 0x0000000184cd0c88 __CFRunLoopDoTimer + 1076
10 CoreFoundation 0x0000000184cd00d8 __CFRunLoopDoTimers + 328
11 CoreFoundation 0x0000000184cc9e8c __CFRunLoopRun + 1944
12 CoreFoundation 0x0000000184cc91c0 CFRunLoopRunSpecific + 600
13 CoreFoundation 0x0000000184cca2ac CFRunLoopRun + 64
14 ARKitCore 0x00000001b07d50b0 -[ARRunLoop _startThread] + 584
15 Foundation 0x000000018611b2fc __NSThread__start__ + 864
16 libsystem_pthread.dylib 0x00000001d0770c00 _pthread_start + 320
17 libsystem_pthread.dylib 0x00000001d0779758 thread_start + 8 -
unity_77abe77
Mar 15, 2021 06:09
* thread #41, name = 'com.apple.arkit.ardisplaylink.0x280646e40', stop reason = EXC_BAD_ACCESS (code=1, address=0xced877900)
frame #0: 0x000000019f100020 libobjc.A.dylib`objc_release + 16
frame #1: 0x00000001b55a513c ARKitCore`-[ARDeviceOrientationData setDeviceMotion:] + 56
frame #2: 0x00000001b55e6e0c ARKitCore`-[ARDeviceOrientationSensor currentData] + 232
frame #3: 0x00000001b557de44 ARKitCore`__40-[ARSession sensor:didOutputSensorData:]_block_invoke_2 + 392
frame #4: 0x00000001b55547d4 ARKitCore`-[ARRenderSyncScheduler _tryNextBlockWithTotalTried:] + 356
frame #5: 0x00000001b555414c ARKitCore`__57-[ARRenderSyncScheduler initWithExpectedFramesPerSecond:]_block_invoke + 40
frame #6: 0x00000001b5588028 ARKitCore`__36-[ARDisplayLink displayLinkCallback]_block_invoke + 64
frame #7: 0x000000018b45db20 Foundation`__NSFireTimer + 68
frame #8: 0x000000018a042fa0 CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 32
frame #9: 0x000000018a042ba0 CoreFoundation`__CFRunLoopDoTimer + 1064 -
unity_77abe77
Mar 15, 2021 06:03
I am on iOS version 14.3
-
unity_77abe77
Mar 15, 2021 06:02
I am also seeing this for face tracking after I leave the app running for a prolonged amount of time.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Resolution Note (2021.2.X):
Our developers have investigated this issue and determined this issue is occurring within iOS 14.2. We have communicated this to our partners. Since we cannot fix this issue, we will be closing it as "Won't Fix".