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
- Errors are logged when importing an asset at a path with Firebase
- Entering too big of a number in 2D Renderer Lightmode Tags freezes the Editor
- Crash on GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
Resolution Note (fix version 1.8.1):
fixed in 1.9.0