Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2021.3.X, 2022.1.X
Votes
1
Found in
2021.2
2021.2.11f1
2022.1
2022.2
Issue ID
1407692
Regression
No
Crash on ShaderLab::Program::GetMatchingSubProgram after entering Play Mode
Reproduction steps:
1. Open the attached project
2. Open "MainScene" Scene
3. Select "Application (Main Client)" GameObject
4. Open the "Backend url" drop-down in the Inspector window
5. Select the URL mentioned in the Edit
6. Enter Play Mode
Reproducible with: 2021.2.14f1, 2022.1.0b11, 2022.2.0a7 (Editor crashes when opening the project)
Could not test with: 2019.4.36f1, 2020.3.30f1 (errors after downgrading the project preventing from entering Play Mode)
Stack trace:
0x00007ff6a771bed1 (Unity) ShaderLab::Program::GetMatchingSubProgram
0x00007ff6a772270c (Unity) ShaderLab::ShaderState::FindSubProgramsToUse
0x00007ff6a77212a6 (Unity) ShaderLab::ShaderState::ApplyShaderState
0x00007ff6a7713957 (Unity) ShaderLab::Pass::ApplyPass
0x00007ff6a76fb26e (Unity) DrawVBOChunkWithPass
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a14
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.2f1