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
- Depth is not rendered in a depth-only camera which is set up by a custom script
- The Scene\Game view is grey when two "Universal Additional Camera Data" scripts are attached to the camera
- NullReferenceException error thrown when changing Scenes in Play Mode
- Crash on "'anonymous namespace'::ConvertFBXShapes" when importing an FBX file
- Crash on Transform::RemoveFromParent when Object.DestroyImmediate() is called on Transform
Add comment