Search Issue Tracker
Fixed in 3.1.2
Votes
1
Found in [Package]
2.3.0
Issue ID
1221972
Regression
No
Crash in ShaderLab::TexEnv::SetTextureInfo when running Play Mode for a while with an invalid Post Processing shader
How to reproduce:
1. Open user-submitted project (ML Shader play 2.zip)
2. Open the SampleScene
3. Note the immediate ArgumentExceptions in the Console window
4. Enter Play Mode and leave it running for a while
Expected result: the Editor does not eventually crash
Actual result: the Editor eventually crashes
Reproducible with: 2018.4.18f1, 2019.3.4f1, 2020.1.0a26, 2020.2.0a1
Could not test with: 2017.4.37f1
Reproducible with package versions: 0.1.7, 2.3.0
Notes:
Reproducible with any invalid shader(e.g. a material renamed to have a .hlsl extension)
The crash occurs after around 1000-5000 error messages are printed in Play Mode, lesser number with newer versions of Unity
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Rendering Debugger" displays incorrect overdraw count when using "Unlit/Texture" shader
- Scene and Game views break when the Editor window is snapped with the Microsoft PowerToys
- Materials do not transfer texture when the "Shader" parameter is changed from "Unlit/Texture" to "Universal Render Pipeline/Unlit"
- [Linux][Vulkan] Crash when opening searchable dialog
- The "Shader error in 'AE/Leaves': "Undefined punctual shadow filter algorithm"" error appears when build completes on a specific project
Add comment