Game crashes in Release exports, no error in Debug (GDScript Pool*Array with type hinted from Array)

[WolfgangSenff]

I have looked for a few other issues and while some might be the same, I have a repro project whereas those did not. It's not a minimal project, but it's easy enough to cause the bug with this project. It might be the same or very similar to #46533, not sure, as I didn't test it just with deleting nodes explicitly (mine happens on scene change).

Godot version:
3.3.stable, GLES2 for web exporting (but happens regardless of which system exported for)

OS/device including version:
macOS Catalina, 10.15.5, Radeon Pro 560X, also integrated Intel UHD Graphics 630

Issue description:
When switching scenes in my game while in release mode, the game often freezes. This happens regardless of which system I'm exporting for. It seems very little is listed in the Mac OS logs as well - I actually couldn't find anything. However, it looks like possibly the web export has a bit more information (but note the freeze is definitely not specific to the web build):

Steps to reproduce:

1. Clone and open the project
2. Export for any platform, without debug info (this is the most important part - it won't crash if you export with debug info); this even happens exporting from Mac to Mac.
3. Run the app from the exported package
4. Play single player
5. Move to the right with D or right arrow, jumping enemies with spacebar or left mouse click until you get to the door and touch the door with your snoot.

For my testing, I found this always froze on the next screen. Since it's picking scenes at random to send you to next, I don't think it's specific to my code, but it's possible, as I use an inherited root scene for each level.

Minimal reproduction project:
I don't have a minimal reproduction, just the big one. I'm not sure exactly what's causing it, but as it's a crashing bug, I think it's pretty important to include it here anyway:

https://github.com/WolfgangSenff/GOTMJam3

[Zireael07]

'function signature mismatch' is an error specific to web build.

Does it happen if you remove the randomizing part of the portal (to exclude the possibility that one of the scenes is corrupted itself)?

[WolfgangSenff]

I'm not sure, but if that's specific to the web build, then maybe it's not actually useful for debugging, doh. It definitely happens on all other platforms as well. However, regarding the randomizing, none of the scenes are corrupted - used to go through them linearly and was still frozen. The randomization was only added toward the end.

[akien-mga]

I can't test the project, the Firebase plugin seems to have missing files:

[WolfgangSenff]

Oh. I must have put that one into my gitignore. Ugh. Let me make a branch that removes it, as it's only used for multiplayer, sorry.

[WolfgangSenff]

For now, if you want, you can grab that file from here: https://github.com/GodotNuts/GodotFirebase/blob/main/addons/godot-firebase/firebase/firebase.gd - it'll cause weird bugs not having the data in there, but only if you try multiplayer. Single player should be fine without the config stuff at the top.

[akien-mga]

Thanks, I can reproduce a segfault on Linux. I'll grab a stacktrace.

[akien-mga]

The crash also happens with 3.2.3-stable so it's not a recent regression.

Crashes here:

Thread 1 "godot.x11.opt.6" received signal SIGSEGV, Segmentation fault.
Variant::call_ptr (this=this@entry=0x4365510, p_method=..., p_args=p_args@entry=0x7fffffffc738, p_argcount=p_argcount@entry=0, r_ret=0x7fffffffc6d8, r_error=...) at core/variant_call.cpp:1165
1165                    funcdata.call(ret, *this, p_args, p_argcount, r_error);
(gdb) bt
#0  Variant::call_ptr (this=this@entry=0x4365510, p_method=..., p_args=p_args@entry=0x7fffffffc738, p_argcount=p_argcount@entry=0, r_ret=0x7fffffffc6d8, r_error=...) at core/variant_call.cpp:1165
#1  0x00000000007f6355 in GDScriptFunction::call (this=0x3ff6b50, p_instance=p_instance@entry=0x4365bc0, p_args=p_args@entry=0x7fffffffc9f8, p_argcount=p_argcount@entry=1, r_err=..., p_state=<optimized out>)
    at modules/gdscript/gdscript_function.cpp:1086
#2  0x00000000007b80f0 in GDScriptInstance::call_multilevel (this=0x4365bc0, p_method=..., p_args=0x7fffffffc9f8, p_argcount=1) at modules/gdscript/gdscript.cpp:1224
#3  0x0000000000ec1d07 in Node::_notification (this=0x4365690, p_notification=<optimized out>) at scene/main/node.cpp:69
#4  0x0000000001384f98 in Node::_notificationv (p_reversed=false, p_notification=16, this=0x4365690) at ./scene/main/node.h:46
#5  CanvasItem::_notificationv (p_reversed=false, p_notification=16, this=0x4365690) at ./scene/2d/canvas_item.h:166
#6  Node2D::_notificationv (p_reversed=false, p_notification=16, this=0x4365690) at ./scene/2d/node_2d.h:38
#7  CollisionObject2D::_notificationv (p_reversed=false, p_notification=16, this=0x4365690) at ./scene/2d/collision_object_2d.h:39
#8  PhysicsBody2D::_notificationv (p_reversed=false, p_notification=16, this=0x4365690) at scene/2d/physics_body_2d.h:43
#9  KinematicBody2D::_notificationv (this=0x4365690, p_notification=16, p_reversed=<optimized out>) at scene/2d/physics_body_2d.h:290
#10 0x0000000001caeda4 in Object::notification (this=0x4365690, p_notification=16, p_reversed=<optimized out>) at core/object.cpp:929
#11 0x0000000000ee2dda in SceneTree::_notify_group_pause (this=0x2ac1370, p_group=..., p_notification=16) at scene/main/scene_tree.cpp:993
#12 0x0000000000ee6ed1 in SceneTree::iteration (this=0x2ac1370, p_time=<optimized out>) at scene/main/scene_tree.cpp:486
#13 0x00000000005961dd in Main::iteration () at main/main.cpp:2100
#14 0x0000000000578731 in OS_X11::run (this=this@entry=0x7fffffffce00) at platform/x11/os_x11.cpp:3641
#15 0x0000000000566035 in main (argc=3, argv=0x7fffffffd6d8) at platform/x11/godot_x11.cpp:56

CC @RandomShaper (in case you're interested in this kind of release-only issue).

[WolfgangSenff]

In case anyone needs the branch upon which I've removed the Firebase-related error that Akien reported above, here you are: https://github.com/WolfgangSenff/GOTMJam3/tree/remove-firebase-for-bugfix