Search Issue Tracker
Duplicate
Votes
0
Found in
5.4.2f2
Issue ID
851438
Regression
No
[Shaders] Shader with a lot of multi_compile/shader_feature variants uses a lot (e.g. 1GB) memory in the Editor
Reproducible with:
5.6.0a3
5.5.0f1
5.4.2f2
5.3.6f1
Reproduction Steps:
1- Download and open the reproduction project. (case_851438-5.4.2f2.zip)
3- Open profiler and profile editor.
4- Check memory usage in detailed mode to see memory usage of assets.
5- See memory usage of custom shaders. (Assets->Shader->StandardZoink...)
Expected Result: Shaders should use few megabytes of memory.
Actual Result: Custom shaders are using ~1 GB memory per each.
p.s. Not reproducible with build of the project. In build, shaders' memory consumption is ~20 KB.
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
This is a duplicate of issue #766056