Internal script error! Opcode: 116 (please report).

[cube-logic]

Tested versions

Reproducible on Godot 4.2.2

System information

Godot v4.2.2.stable - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4070 Ti (NVIDIA; 31.0.15.5244) - 12th Gen Intel(R) Core(TM) i9-12900K (24 Threads)

Issue description

Random crashes with no warning or Internal script errors (every time I run it's something else)
I have a big project I'm working with around 50 gdscript files different player states
The project always crashes on interaction (any) and leaves me with different error codes


Or just a random crash with no error code or warning
I couldn't figure out what happens on which interaction, I just know it happens with await
Please tell me if there is a way I could debug this myself since every time I run the project godot says it's a different file that causes the issue, never one specific file

Steps to reproduce

I wish I knew, it happens mostly with await and specifically on waiting for animations with await animation_player.animation_finished (that was how I fixed the same problem last time)

Minimal reproduction project (MRP)

I couldn't remake the project and get the same error, only in this big project I've seen it happening

[dalexeev]

Sorry to hear that you encountered such a bug. Does the bug happen when you edit a script while the project is running (we have some problems with hot reloading)? If not, you can try the following algorithm to isolate the bug and create an MRP:

Make a copy of your project and iteratively remove parts that are probably not relevant to the bug. Check after each iteration to see if the bug is still reproducible. If it remains, try removing something else. If it disappeared, go back to the previous step and try to remove something else. Keep doing this until the project is small enough or it's clear what's causing the problem.

Also, have you checked whether the bug is reproducible on 4.3 dev 6 (make a backup before checking)? If there is some chance that it has already been fixed, it makes sense to check that first, since it will take much less time than the described above.