Search Issue Tracker
Fixed in 2020.2.X
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a1