Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.3.X, 2020.1.X
Votes
0
Found in
2018.4
2019.3.6f1
2020.2
Issue ID
1227997
Regression
No
[iOS] Texture.currentTextureMemory value does not update and a memory leak occurs when enabling and disabling texture streaming
How to reproduce:
1. Open the supplied project from the Google Drive link
2. Open the SCENE_NAME Scene and build it for iOS
3. Deploy the build, then open Xcode's Debug navigator and observe the Memory
4. In your device, tap the buttons "open", then "close"
5. Observe the unchanged value of "streamTextureMemory" and the memory leak occurring in Xcode
6. Wait for the memory to reach the limit and cause a crash
Expected result: the memory leak does not occur
Actual result: memory leaks when stopping streamingMipmapsActive
Reproducible with: 2018.4.19f1, 2019.3.7f1, 2020.1.0b3, 2020.2.0a4
Could not test with: 2017.4.38f1 due to texture streaming being unavailable
Reproduced on: VLNQA00160 iPhone 6S iOS 13.3.1
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
- Intensity parameter ignores Culling Mask causing incorrect lightning when additional lights are disabled
- Input.GetKeyUp is true only for the first released mouse button when releasing mouse buttons outside the Game view
- Physics objects trip and/or jump when colliding with other colliders
- [Package Manager] Release Details of Assets include HTML tags
- Rigidbody2D.IsTouching does not return true on collision for its duplicate GameObjects when ContactFilter2D and LayerMask are used
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a8
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b6
Resolution Note (fix version 2018.4):
Fixed in 2018.4.23f1