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
- [VFX Graph] ArcCone Direction computation is wrong in Base Mode
- [Android] [Galaxy Tab] A singular Pen touch logs a Pen touch event and a singular finger touch event when logged using "VisualElement.RegisterCallback" with "Pointer(Up/Down)Event"
- Crash on D3D12DescriptorCache::Deallocate or vkGetInstanceProcAddr when loading RenderDoc in a specific Scene
- [HDRP] Lit material preview is rendered incorrectly with a mask map
- The "LerpWhiteTo" missing function displays an error when the Shadows.hlsl shader is included in a Shader file
Add comment