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
- After converting a Built-in project to URP render texture related errors are spammed that can lead to Game view being rendered on top of Scene view
- UI Builder slider value lags and stutters when sliding/modifying certain property values
- "Reset UI Builder Layout" functionality inconsistently changes Canva Size when "Match Game View" is enabled/disabled
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
Add comment