Search Issue Tracker
Fixed
Fixed in 2022.3.21f1, 2023.3.0a16
Votes
0
Found in
2022.3.12f1
Issue ID
UUM-54697
Regression
Yes
[iOS] Crash when running Shader.WarmupAllShaders() after application start
How to reproduce:
1. Download and open the attached "EmptyWarmupTest" project
2. Build and deploy to iOS
3. Tap the device screen
4. Observe the crash
Reproduced with: 2022.3.10f1, 2022.3.12f1, 2023.1.19f1, 2023.2.0b16, 2023.3.0a12
Not reproducible with: 2021.3.32f1, 2022.3.9f1
Reproduced on: VLNQA00310 iPad Pro 12.9'' (iOS 13.4.1), iPhone XS (iOS 16.6.1)
Could not reproduce on: VLNQA00416 iPhone 13 Pro (iOS 16.1.1),
VLNQA00494 iPhone 14 Pro Max (iOS 16.3.1),
VLNQA00358 iPhone 12 (iOS 14.1)
VLNQA00359 iPhone 12 Pro (iOS 14.2.1)
Notes:
Running Shader.WarmupAllShaders() during the Start method does not crash.
Running it after application startup (by which I mean, in an update loop) causes the crash.
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 (fix version 2023.3.0a16):
Verified with: 2023.3.0a16
Resolution Note (fix version 2022.3.21f1):
Verified with 2022.3.21f1