You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've found several similar issues, but it looks little different
Godot version:. v3.2.3.stable.official
Issue description:
ERROR: ~List: Condition "_first != __null" is true.
At: ./core/self_list.h:112.
ERROR: ~List: Condition "_first != __null" is true.
At: ./core/self_list.h:112.
Leaked instance: GDScript:6304 - Resource path:
Leaked instance: GDScriptNativeClass:669
Leaked instance: GDScriptNativeClass:802
Leaked instance: GDScript:6303 - Resource path: res://Logger.gd
WARNING: cleanup: ObjectDB instances leaked at exit (run with --verbose for details).
At: core/object.cpp:2135.
Hint: Leaked instances typically happen when nodes are removed from the scene tree (with `remove_child()`) but not freed (with `free()` or `queue_free()`).
ERROR: clear: Resources still in use at exit (run with --verbose for details).
At: core/resource.cpp:477.
Resource still in use: res://Logger.gd (GDScript)
Steps to reproduce:
Please add below code into empty project and add it to AutoLoad.
Add export presses "Linux/X11".
Export it with next command:
PS: Please surround large blocks of text with triple backticks like this:
```
text here
```
For syntax highlighting, use:
```gdscript
text here
```
This prevents them from taking too much space and also makes sure issue references aren't accidentally created. I edited your comment, but remember to do this next time 🙂
At first: thank you all for the amazing engine!
I've found several similar issues, but it looks little different
Godot version:. v3.2.3.stable.official
Issue description:
Steps to reproduce:
Please add below code into empty project and add it to AutoLoad.
Add export presses "Linux/X11".
Export it with next command:
Removing 'LoggerNode' type hints or removing the script from AutoLoad (of course attach it to any scene) solve the leak.
The text was updated successfully, but these errors were encountered: