Search Issue Tracker
Fixed
Fixed in 2022.3.28f1, 6000.0.1f1
Votes
1
Found in
2022.3.25f1
2023.2.19f1
6000.0.0b16
Issue ID
UUM-70277
Regression
Yes
Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
How to reproduce:
1. Open the attached “ShaderReproProject“ project
2. Open the “Assets/Scenes/Oasis/OasisScene.unity“ Scene
3. Enter Play Mode
Reproducible with: 2022.3.25f1, 2023.2.19f1, 6000.0.0b16
Can’t test with: 2021.3.37f1 (Errors in the Console due to downgrading project)
Reproducible on: macOS 14.4 Sonoma (Intel)
Not reproducible on: No other environment tested
Notes:
- Also reproducible in Player
- User noted that removing the dynamic branch from FoveatedRenderingKeywords.hlsl prevents the crash
First few lines of the stack trace:
0x00007ff652fa9f6a (Unity) ShaderLab::ShaderState::ApplyShaderState
0x00007ff652f9b7e4 (Unity) ShaderLab::Pass::ApplyPass
0x00007ff652f85755 (Unity) DrawVBOChunkWithPass
0x00007ff652f8daba (Unity) ShaderWarmupFuncImpl
0x00007ff652f8ed19 (Unity) ShaderVariantCollection::WarmupOneShaderImpl
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment