Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2020.1.X
Votes
0
Found in
Issue ID
1253081
Regression
Yes
[Shader Compiler] Surface shader compilation makes Unity Shader Compiler processes stay at over 700 MB ram usage
STR:
1. Make sure Caching Preprocessor is turned on.
2. Copy Particles/Standard Surface shader to a new project.
3. Look at memory consumed by Unity Shader Compiler processes.
Expected: memory should go back to some low value (e.g. 100 MB) after import
Actual: memory stays at some high value even when import is finished (e.g. 400+ MB).
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0a15
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0b13