Search Issue Tracker
Fixed in 2020.2
Votes
0
Found in
2018.4.0f1
2019.1.0a1
2019.1.8f1
2019.2.0a1
2019.3.0a1
Issue ID
1167280
Regression
No
Memory leak occurs due to TransformStreamHandle memory not being deallocated when deactivating GameObjects
How to reproduce:
1. Open user-submitted project (Repro_project-leak-685090)
2. Open the Profiler window and click on the 'Memory' section
3. Enter Play Mode
4. Click the space key repeatedly to imitate pooling
5. Observe the 'AnimationClips' allocated memory in the Profiler window
Expected result: memory is deallocated when the objects are deactivated
Actual result: memory is not deallocated when the objects are deactivated; a memory leak occurs
Reproducible with: 2018.3.0a6, 2018.4.3f1, 2019.1.9f1, 2019.2.0b9, 2019.3.0a8
Could not test with: 2017.4.29f1, 2018.3.0a5(Incompatibility issues)
Notes:
Workaround: Destroying the Animator Component re-creating it releases memory for StreamHandles
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
- Shadows are not cast when you first Blit the Shadow map and then set it back to Buffer
- Changes to instanced detail mesh material don't immediately apply
- [uGUI] Vertices retrieved from GetUIVertexStream method cannot be modified when adjusting them through script
- Scroll bar scrolls less in the Package Manager packages than elsewhere when pressing on the empty scroll bar area to scroll
- Undo.RegisterCreatedObjectUndo dirties the scene, but no actual changes to Scene are made
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a1