Search Issue Tracker
Fixed
Fixed in 2021.3.18f1, 2022.2.5f1, 2023.1.0b1
Votes
1
Found in
2021.3.16f1
2022.2.2f1
2023.1.0a25
Issue ID
UUM-21964
Regression
No
iOS Player crashes on "UnityGfxDeviceWorker" when a specific prefab is in the scene
How to reproduce:
1. Open the user’s attached “Spaceschuter McGavin.zip” project
2. Add “Hermes 1.prefab” or “Hermes 5.prefab” to the Scene
3. Build And Run the project on an iOS device
4. Observe the result
Expected result: No crash
Actual result: Crash and Xcode logs “UnityGfxDeviceWorker (38): EXC_BAD_ACCESS (code=1, address=0x30e56)“ or “UnityGfxDeviceWorker (30): EXC_BAD_ACCESS (code=1, address=0x30e56)”
Reproducible with: 2021.3.16f1, 2022.2.2f1, 2023.1.0a25
Could not test with: 2020.3.44f1 (Errors after project download)
Reproduced on:
VLNQA00494 - iPhone 14 Pro Max, 16.0.3 iOS
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00392 - iPad (9th generation), 15.0 iOS
VLNQA00310 - iPad Pro 12.9", 13.4.1 iOS
Not reproduced on:
Android (user’s info)
macOS 12.4 (Intel)
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
- Resources.UnloadUnusedAssets() freezes the Editor when releasing Mesh objects
- 16-bit Sprite Textures have a banding effect and loss of data when packing into Variant Sprite Atlas
- HDRP Cluster artifacts when having more than 100 lights
- ParticleCollisionEvent.intersection generates extremely high values when particles collide while in Play Mode
- Custom attributes are not properly converted to subgraphs
Resolution Note (fix version 2023.1.0b1):
Fixed in: 2023.1.0b1
Resolution Note (fix version 2022.2.5f1):
Fixed in: 2022.2.5f1
Resolution Note (fix version 2021.3.18f1):
Fixed in: 2021.3.18f1