Open MikeSchulze opened 1 year ago
The same in the current master
[5dccc940e73d39a1ac4f3d64ccc92373e6609add].
Hello, what is the current status on the subject? The amount of orphaned objects is smoothly overwhelming ;)
what is the current status on the subject?
I can see/tell as much as you do: no one said anything in here, no linked PR / other issues. So I'd guess no one investigated this. I'll put a link at the contributor's chat, maybe someone will get interested.
it sill occurs on v4.1.stable.official [970459615]
Godot version
v4.0.stable.official [92bee43ad]
System information
Windows 10
Issue description
Using await results in memory leak.
I got a lot of orphan nodes at exit after execution my test coverage (using GdUnit4). The tests uses some stuff around timeouts and await for signals and function results.
I've boiled it down so far, and it looks like a simple "await get_tree().process_frame". already suffices to get orphan nodes,
I found this issue https://github.com/godotengine/godot/issues/57126, but it is already closed.
And also a lot of orphan
StringName
are found, i guess this is already adressed.Steps to reproduce
execute the attached scene by
Godot.exe --verbose -d res://Orphans.tscn
Minimal reproduction project
orphan_await.zip