Search Issue Tracker
Not Reproducible
Votes
1
Found in
2022.3.10f1
2023.1.11f1
2023.2.0b8
2023.3.0a4
7000.0.0a1
Issue ID
UUM-49629
Regression
No
[Win] Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode after saving a Shader Graph
Reproduction steps:
1. Open the attached project “CrashRepro“
2. Open “SHADER“ Shader Graph
3. Change something in the Shader Graph (Connect “Use Color Grading“ output to “Emission“)
4. Save the Shader Graph
5. Enter the Play Mode
6. If it does not crash press any button on the keyboard and click on the “Play“ button
Expected result: The Play mode continues
Actual result: Editor crashes
Reproducible with: 2022.3.10f1, 2023.1.11f1, 2023.2.0b8, 2023.3.0a4
Couldn’t test with: 2021.3.30f1 - (Shaders are pink and errors are thrown: “State comes from an incompatible keyword space“)
Reproducible on: Windows 10
Not reproducible on: No other environment tested
First few lines of stack trace:
{noformat}0x00007FF90F7A8018 (Unity) ShaderLab::ShaderState::ApplyShaderState
0x00007FF90F7997A7 (Unity) ShaderLab::Pass::ApplyPass
0x00007FF90F72DBA1 (Unity) ApplyMaterialPass
0x00007FF90F41F9FD (Unity) BatchRenderer::ApplyShaderPass
0x00007FF90F41FBCE (Unity) BatchRenderer::ApplyShaderPass{noformat}
Note: The reproduction rate seems to be around 70%
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
- Editor default Stylesheet/Matching Selector buttons in Debugger don't do anything
- Graphics.DrawMeshNow stops rendering Render Texture after a few frames when viewed in the Player
- New selector in Matching Selectors displays as on line -1 in debugger
- The first frames are skipped when playing a video
- Text auto-scrolling can not work when naming assets/objects until backspace key is pressed
Resolution Note:
Was able to reproduce only in the reported version, but not in newer versions, so this may have already been fixed.