WARNING: ObjectDB instances leaked at exit #62
Replies: 2 comments
-
Okay, I think it's my code. I did some stuff to make callbacks get cancelled almost instantly when I want to stop the code, and made quitting stop the code, and I reduced it down to the following:
No more orphaned string names. Still not sure what to do about the rest. |
Beta Was this translation helpful? Give feedback.
-
Hey @OvercookedBeef, are you using Lua to script Godot objects or only as a modding/external scripting tool? I finally fixed some leaks when using Lua to script Godot objects, we had cyclic dependencies from LuaScript and LuaScriptProperty to their owning LuaState, so that any Godot objects referenced in Lua would leak forever 😬 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm not sure if I'm doing something wrong or if it's a bug, so I made a discussion instead of an issue.
When making my game inside the engine, everything worked perfectly. But I now exported my project, and it has an issue when the player quits the game. When they try to quit, the window freezes and I get the following from console:
Do I need to clean this up some how? I tried calling
.free()
on the LuaState, but that gave meAttempted to call free a RefCounted object.
(If this isn't related to the library, then oops, sorry)
Beta Was this translation helpful? Give feedback.
All reactions