Search Issue Tracker
Fixed in Unity 2017.3.0f3
Votes
0
Found in
5.6.1f1
Issue ID
919162
Regression
No
Texture2DArray.Apply(makeNoLongerReadable: true) doesn't free heap memory
How to reproduce:
1. Open user provided project
2. Build standalone or to mobile device
3. Inspect heap memory
Expected behaviour: Using Texture2DArray.Apply(makeNoLongerReadable: true) should act like Texture2D.Apply(makeNoLongerReadable: true) and release heap memory
Actual behaviour: The memory does not get released.
Reproduced on: 5.5.4f1, 5.6.1p3, 2017.1.0b9, 2017.2.0a3
Reproduced using: iOS, Mac and Android
Fixed in: 2017.3.0a2
Backported to: 5.6.3p1, 2017.1.0p3, 2017.2.0b5
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The "Materials" tab in the Inspector window is empty when inspecting an imported .fbx file
- Using the Reset() context menu option on a Scriptable Object clears its name property in the Inspector window
- [OSX] Unity beachballs when coming out of sleep
- [Android, iOS][Touch] Touch is 1-2 frames late
- [XR] InputDebugger does not update consistently to reflect movement or interaction
Add comment