-
-
Notifications
You must be signed in to change notification settings - Fork 21.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GDScript 2.0: Massive memory leaks when running a script via command line #68009
Comments
My PR #67714 does not fix the leak, but it reduces its scope.
|
@Chaosus, @Calinou Here an small tool to find Engine core orphan nodes. Looks like there is also a chaching issue. |
) # Why Running the `GdUnitCmdTool` ends with an signal 11 and many orphan resource detected # What - fixed the signal 11 by using a copy to iterate over singletons before freeing - when iterating over an array and removing elements during the iteration, godot ended up with signl 11 - moving the func `assert_failed_at` to another posision (very strange results, it crashed for no reason) - using typed array on `load_testsuites()` - fix some orphan issues around singleton implementation - centralize code to finaly cleanup in new `quit` function to avoid orphan nodes - format touched code according to code style # Note It still detects orphan nodes see: godotengine/godot#68009
Hello, what is the current status on the subject? StringName: 871 unclaimed string names at exit. |
Hi, if there some update here? |
Leaks of this kind are fixed on a best-effort basis, when contributors are available to do so. As a result, we can't give an ETA for fixing this. |
Also having this issue when exporting using 4.2.1.stable.
Adding my GDExtension to the project changes the output to a lot more orphaned string names
Also, on Windows, closing the exported project window takes ~15 seconds for it to exit and prints
(not sure if this is related though). |
Godot version
v4.0.beta3.official [01ae26d]
System information
Windows 10
Issue description
I deployed a command line tool as SceneTree and it ends up with very many orphaned nodes.
Mainly
StringNames
orphans are detected.And it also looks like classes with functions that return themselves are not handled correctly either.
Also singletons are not freed.
Steps to reproduce
I attached an small example project with example cases that results into orphan node detection.
Open a console and run:
Godot_v4.0-beta3_win64.exe --no-window -s -d CmdTool.gd --verbose
The output:
Minimal reproduction project
orphan.zip
The text was updated successfully, but these errors were encountered: