Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.2.0a8
2019.3
2019.3.0b11
2020.1
Issue ID
1200485
Regression
Yes
Creating temporary RenderTextures with a RenderTextureDescriptor severely bloats Texture Memory
How to reproduce:
1. Open user-submitted project (TtempRT_desc2019.3)
2. Open the SampleScene
3. Enter Play Mode
4. Open Window > Analysis > Profiler
5. See the Memory module, Textures memory
Expected result: the allocated memory is no more than a few hundred MB
Actual result: the allocated memory is over a few GB
Reproducible with: 2019.2.0a8, 2019.2.14f1, 2019.3.0f1, 2020.1.0a15
Not reproducible with: 2017.4.35f1, 2018.4.13f1, 2019.2.0a7
Notes:
Testing with the same project the following Textures memory has been observed in different versions:
2017.4.35f1: Textures: 2084 / 20.7 MB
2018.4.13f1: Textures: 291 / 192.7 MB
2019.2.0a7: Textures: 1028 / 194.4 MB
2019.2.0a8: Textures: 1053 / 6.06 GB
2019.2.14f1: Textures: 346 / 6.20 GB
2019.3.0f1: Textures: 723 / 6.21 GB
2020.1.0a15: Textures: 751 / 6.22 GB
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Building 3D Sample Scenes (URP) Project fails
- Alpha channel is disabled when Alpha Clip Threshold is set to 0
- The Physics 2D Profiler module does not display the information about processed physics in the scene when profiling the application as a Development Build
- A Script Component that has a serialized custom class is not detecting changes in the first boolean variable when entering the Play mode with the Script Components GameObject opened in the Inspector
- “SendMessage cannot be called during Awake“ warnings appear when loading a scene with “LoadSceneAsync“ if using UI Toolkit in the scene
Add comment