Search Issue Tracker
Fixed in 2023.1.4f1
Fixed in 2023.1.X, 2023.2.X, 2023.3.X, 2023.3.0a1
Votes
0
Found in
2023.1.0b10
2023.2.0a9
2023.3.0a1
Issue ID
UUM-32171
Regression
Yes
`Texture.nonStreamingTextureMemory` is increased each time when entering Play Mode
Reproduction steps:
1. Open the “TextureStreamingStripped“ project
2. Open the “SampleScene” scene
3. Enter the Play Mode a few times while observing the Console
Expected result: each time {{Texture.nonStreamingTextureMemory}} is the same
Actual result: each time {{Texture.nonStreamingTextureMemory}} is increased by ~1000000
Reproduced in: 2023.1.0a20, 2023.1.0b10, 2023.2.0a9
Not reproduced in: 2020.3.47f1, 2021.3.22f1, 2023.1.0a19
Reproduced using: Windows 11, macOS 13.2.1 (Intel), macOS 12.4 (M1)
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (fix version 2023.3):
Fixed issue with font asset being re-created every domain reload
Resolution Note (fix version 2023.2):
Fixed issue with font asset being re-created every domain reload
Resolution Note (fix version 2023.1):
Fixed issue with font asset being re-created every domain reload