Godot Version
v4.2.2.stable.mono.official [15073afe3]
Question
So I’m not even sure where to start with this one. I’ve been SOMETIMES getting these error messages WHEN I exit my game, but only sometimes. I cannot reproduce it consistently, as it won’t always show up, but sometimes, after I exit my game, my IDE reports the following errors and warnings:
As I said, not always, and even when I do get them, it’s always something different, sometimes only one item, sometimes multiple ones like this. I can’t reproduce it consistently, it just sometimes happens and sometimes doesn’t, and it never CRASHES the game, these always come up after I exit the game.
I’d appreciate any help or direction on what these might be or where to go from here to figure out what’s causing them, as they’re becoming increasingly more worrying as I get closer to release. Thank you!
I tried to reproduce the issue to be more consistent, but it’s really difficult to do without knowing which scripts are actually generating the issue, and using the mentioned verbose mode won’t really give me any specifics either, only things from the C++ source code. Any ideas?
If these errors are occurring when closing the game then I wouldn’t be too worried.
This is probably happening when the game is being offloaded from memory and so some things are still running and leak because other components they depended on were offloaded before they were.
I know a game made in Godot on Steam that constantly throw these errors when closing the game and it doesn’t break anything.
I ran into this today when I was fiddling with one of my scenes.
I’m not really sure what I did to cause the issue but I was able to dig down into this further using the verbose flag,
&"Path/To/Godot/Godot_v4.3-stable_mono_win64.exe" --path "./" --verbose
This is from PowerShell so & to execute the string as a command, and path set to local directory as I was running direct from the project folder.
This returned the main resource that got stuck, a single texture that I only had on a scene that was loaded multiple times in a parent scene. Looking at that parent scene in the text editor showed that there was a name collision somehow.
There were multiple instances of the node with the same name, where only one was showing in the editor.
I deleted these all from the text file, reloaded the editor and re-instanced the scenes and no more errors.
Hope this helps someone stumbling across this in future!
1 Like
Unfortunately my issue here is that, while I tried something similar before, every single time I get something like this:
I cannot find that Node, as I don’t know what that number actually is, I tried listing ALL the nodes during the running game and print whatever ID they had, but nothing matched that specific ID, and the fact that “Node name” is empty, I literally have no idea where to look.
1 Like
That’s a shame. Definitely different to what I saw.
Sorry I didn’t help.
