Search Issue Tracker
Fixed
Votes
0
Found in
2019.3.0b9
2019.3.7f1
2020.1.0a2
Issue ID
1232610
Regression
Yes
Exceeding the number of shader keywords flood the console with Allocation errors
How to reproduce:
1. Open the attached project named "Case_1232610"
2. Observe the Console window if no errors are thrown re-import the
Expected result: Only errors related to the exceeded number of shader keywords are thrown
Actual result: Additional Allocation errors are thrown
Reproducible with: 2019.3.0b9, 2019.4.0f1, 2020.1.0a2, 2020.1.0a18
Not reproducible with: 2018.4.25f1, 2019.3.0b8, 2019.4.1f1, 2019.4.5f1, 2020.1.0a1, 2020.1.0a19, 2020.1.0f1, 2020.2.0a18
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
- [Android] Light2D with Light type "Spot" does not work in the Player on some Pixel devices
- [Android] Loading the asset using an old reference returns null even when the "FormerlySerializedAs" attribute is used
- Crash on ParticleSystemTrailGeometryJob::RenderJobCommon when changing trail Mode change with a large particle count
- Mouse cursor does not revert to the default mouse cursor when pressing the "Add column" button in the Search window
- ArgumentException is thrown and textures become unreadable when AssetBundle.Unload(false) is called
Resolution Note:
Fixed in - 2019.4.1f1, 2020.1.0a19, 2020.2.0a1. A re-import of all assets or clearing the Project's Library might be necessary for the fix to work