Search Issue Tracker
Fixed
Fixed in 1.8.1
Votes
1
Found in [Package]
1.7.8
Issue ID
UVSB-2427
Regression
No
Memory leak after destroying object
h2. Procedure:
# Open the attached project.
# Load the Sample Scene.
# Enter playmode.
# Press C to instantiate a game object with a script machine.
# Press M to destroy the game object.
# Open the memory profiler under Window -> Analysis -> Memory Profiler and capture a new snapshot.
# Go to the tree map and filter for scriptmachine.
!image (2).png|width=487,height=608!
!image (3).png|width=493,height=1001!
h2. Outcome:
The scriptmachine is still in memory.
!image (4).png|width=1007,height=1043!
Reproducible in VisualScripting {*}1.7.8{*}, *1.6.1,* *1.5.1* on Unity {*}2021.3.11f1{*}, *2020.3.35.f1*
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 1.8.1):
fixed in 1.9.0