Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GDScript 2.0: Stack overflow regression #61494

Open
unfa opened this issue May 28, 2022 · 3 comments
Open

GDScript 2.0: Stack overflow regression #61494

unfa opened this issue May 28, 2022 · 3 comments

Comments

@unfa
Copy link

unfa commented May 28, 2022

Godot version

4.0 dev (7b8c574) nightly after 30th of April

System information

Arch Linux, KDE Plasma, Radeon RX580, amdgpu driver, Vulkan

Issue description

After testing my game in nightly builds of Godot 4.0 dev, starting with commit 7b8c574401b3b3a211fd478eaa3fbb99b6dbb798 (not strictly bisected) I am experiencing a Stack Overflow error, while previously it wasn't there, even though nothing in the game's code has changed:

Clipboard - May 22, 2022 6_00 PM

This error was first noticed in a dev build from commit 7b8c574
The last known working Godot 4.0 dev commit is 8adf048

A regression must have been introduced somewhere between these two commits.

Steps to reproduce

  1. Clone and my project Liblast from this specific commit: https://codeberg.org/unfa/Liblast/src/commit/31aefa29dcd62e637dcd203e77602f051a68c320 (the project uses LFS, so make sure you clone that as well - if in doubt please refer to this section of project's README)
  2. Open the scene Game/Assets/Tests/Characer Test.tscn
  3. Hit F6 to play the curent scene.
  4. Observe a stack overflow error.

Minimal reproduction project

No response

@Calinou Calinou added this to the 4.0 milestone May 28, 2022
@Calinou Calinou changed the title Stack overflow regression GDScript 2.0: Stack overflow regression May 28, 2022
@kyleguarco
Copy link

Duplicate of #61130?

@dalexeev
Copy link
Member

dalexeev commented Feb 9, 2023

Please check it out in 4.0 RC 1. If the error is still reproduced, please report it and add an MRP.

@vnen
Copy link
Member

vnen commented Feb 22, 2023

I would like to a see a new test too, as this might have been fixed not long after reported by #62462.

@vnen vnen removed this from the 4.0 milestone Feb 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants