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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
This is a duplicate of issue #766056