Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.3.X
Votes
0
Found in
2018.4
2021.1
Issue ID
1296101
Regression
No
Shaders take a lot of memory at runtime even when only one variant is used
STR:
1. Make a new project from 3D template
2. Put the attached shader into the assets, create a material, assign the shader to the material.
3. Create a cube, assign the material from the previous step to the cube.
4. Build and run (development build).
5. Capture a memory snapshot using the Profiler.
6. See that the shader takes over 140 MB (Mac, idk how much Windows will show, should be a lot as well)
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
- Tilemap Tiles do not get lit up unless the Light Range is greater than the distance between the position of the Tile before the transformation and the Light Source when the Tile is transformed with Tilemap.SetTransformMatrix method
- The Editor and "Reloading Domain" windows are frozen when entering Play Mode
- Crash when attempting to create a custom FMOD DSP unit
- [Linux] Floating windows do not keep their size after restarting the Editor
- .framework plugin is mistakenly treated as a directory when building for Universal Windows Platform
Resolution Note (fix version 2021.1):
Fixed in 2021.2.0a3
Resolution Note (fix version 2021.1):
Fixed in 2021.1.1f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.2f1