Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2021.2.X
Votes
1
Found in
2021.2.0a16
2021.2.0b8
2022.1
Issue ID
1360664
Regression
Yes
Crash on keywords::KeywordRemap::Init when importing specific shaders
How to reproduce:
1. Try to open the project from "SHADERScrash1360664.zip"
2. Observe crash
Reproducible with: 2021.2.0a16, 2022.1.0a9
Not reproducible with: 2019.4.30f1, 2020.3.18f1, 2021.1.22f1, 2021.2.0a15
First lines of stack trace:
0x00007ff7fc2ea5d3 (Unity) keywords::KeywordRemap::Init
0x00007ff7fc2f06ca (Unity) ShaderLab::IntShader::CreateKeywordRemap
0x00007ff7fc2f298a (Unity) ShaderLab::IntShader::ResolveFallback
0x00007ff7fc29deb8 (Unity) ShaderLab::IntShader::CreateFromSerializedShader
0x00007ff7fc2a9328 (Unity) ShaderFromSerializedShader
0x00007ff7fdc0fa1f (Unity) Shader::CreateFromParsedForm
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.1):
Fixed in 2022.1.0a11
Added error logs in the console
Resolution Note (fix version 2021.2):
Fixed in 2021.2.1f1