Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 5.5.X, 5.6.X, 2017.1.X, 2017.2.X
Won't Fix in 5.4.X
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
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
- Crash on GizmoDrawingPhysics2D::DrawCompositeCollider2DGizmo when opening a Scene that has corrupted GameObjects with Tilemap Components
- Scrolling vertically and horizontally is very fast when in Play Mode and RuntimeInputBackend is set to UIToolkitInputBackendOption.Default
- Crash on MemoryProfiler::UnregisterAllocation when initializing entities and leaving Play Mode with Occlusion Culling enabled
- Crash on mdb_page_alloc when opening a project that was running while the PC shut down
- macOS Player freeze when using RunInBackground and Command+Tabbing to and from the application
wenluzhil
Feb 26, 2020 15:44
I have the same question, how can solve ?