error : Resumed after yield, but class instance is gone ???

siska

Hi,

I started noticing this error after migrating my code to Godot 3.1 .My game is still in development, so I don't recall at what point exactly this error started popping up.

The complete error msg I get is this : E 0:00:17:0485 Resumed after yield, but class instance is gone <C Source> modules/gdscript/gdscript_function.cpp:1771 @ _signal_callback()

... which is really not very informative. :'( I have spent quite a bit of time on this already, but no success so far.

My question : is there any way to have the stack trace spit out more information about which node is causing this to happen ?

This is Godot 3.1 / Windows10.

Ace_Dragon

Godot 3.1 has more types of error reporting now, now the output window will print things about your scripting that could potentially lead to errors. You can choose to silence them if you want, as they are mainly supposed to be helpful pointers to help you avoid bugs.

In general, this error occurs when a function is paused by yield, but the object containing the script is discarded before the function resumes (either from the use of functions like queue_free() or from the scene being changed). Your game is not going to stop working otherwise.

TwistedTwigleg

The terminal/console running the Godot editor might point to the line of code that is causing the issue. Generally the error outputs there are a bit more verbose.

I haven't used it myself, so I don't know how it works or how useful it will be, but you can enable a command line debugger by adding -d when you launch the game (and maybe the editor?) according to the documentation. Apparently adding --verbose might help too.

siska

Interesting to read that Godot 3.1 has more extensive error reporting. Definitely a good thing ! I just wished the error would leave me with some sort of a clue as to what caused the problem in the first place. It must have some sort of reference to that object, or else it wouldn't event know to report that something isn't quite right ?!

I am a bit worried about this causing problems once the game has been exported. I saw a bunch of bug reports about the same error on Android (Godot 2.9 or 3.0 ???) which crashed the game ...

Allright. I'll just go over all my code -again- and give some special care to the things you mentioned. Thanks !

siska

@TwistedTwigleg

I asume you'r talking about the Windows command line tool (well, In Windows, obviously) that pops up when you run the game in the editor ? You can set that in proj setts / general / debug /settings / stdout : verbose

Unfortunately, the error message is exactly the same.