Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2019.2
2019.2.7f1
Issue ID
1191954
Regression
No
[iOS 12] [Metal] IOAF code 4 error freeze because of tessellation shader
How to reproduce:
1. Build the attached project for iOS (link in description)
2. Build & Run the project to a device via Xcode
3. Keep clicking buttons shown in screenshots (screenshots in edit)
Actual result: The Player freezes and errors are getting spammed.
Expected result: The Player doesn't freeze.
Reproducible with: 2018.4.11f1, 2019.2.10f1.
Devices reproducible with:
- iPhone XR (iOS 12.0)
- iPhone X (iOS 11.3.1)
Devices not reproducible with:
- iPhone X (iOS 13.0)
- iPhone 7 (iOS 12.3.1)
Notes:
- Can't test 2017.4, 2019.3 and 2020.1 as the terrain completely breaks on these versions, but most likely the issue is reproducible there too.
-
krisnx
Aug 06, 2020 08:00
Hi,
We are getting the similar crash with the below error trace
Unity version : 2019.4.1f1
Device : IPAD 6th generation
IOS version : 12.2Error Trace:
Execution of the command buffer was aborted due to an error during execution. Discarded (victim of GPU error/recovery) (IOAF code 5)
Execution of the command buffer was aborted due to an error during execution. Discarded (victim of GPU error/recovery) (IOAF code 4)
Execution of the command buffer was aborted due to an error during execution. Discarded (victim of GPU error/recovery) (IOAF code 2)Thanks,
Navaneetha.
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (2020.1.X):
This is iOS 12 related, which has decreasing adoption. mostly A7/A8 stick to iOS 12 where tessellation is not a realistic use case, rest of the devices are typically iOS 13 by now
No update from Apple about the filed bug report for workarounds. (will recheck with them)
closing due to very low impact