godotengine / godotengine/godot
Godot 4.3 Beta Crash Bug - Advanced Signals in Editor
- Dominant language
- C++
- Stars
- 117k
- Forks
- 26.8k
- PR merge metrics
- PR metrics pending
Description
### Tested versions
Reproducible in: 4.3 dev 6, NOT reproducible in: v4.1.3.stable.official [f06b6836a]
### System information
Windows 10, MSI Laptop, 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz 2.30 GHz, 16GB Ram, NVIDIA GeForce RTX 3070 Laptop GPU
### Issue description

When trying to connect a signal to a script in the scene tree (in the example image: connecting the "pressed" signal of "button" to the parent nodes script), the signal properties popup window appears, however, when pressing the "advanced" button (to access advanced signal properties within the popup window), Godot will crash. Even bigger issue however! is that when reloading the project, trying to open any signal menu (by trying to connect a new signal: from anywhere, to anywhere) Godot will again crash, making the project unable to connect any new signals via the editor
### Steps to reproduce
1. Have a scene tree with at least one node containing a script, example: A single "control" node with a blank script attached
2. Create a child "button" node
3. In the editor, go to the "button", and try connect a signal from the "Signals and Groups" tab
4. with the signal popup window now opened, press the sliding button named "advanced", towards the bottom of the popup window
5. Godot crashes
6. Restart Godot and reload the same project
7. attempt to open the signal popup window again via the "Signals and Groups" tab
8. Godot crashes as soon as the popup window opens, preventing the ability to connect signals via the editor
9. Sadness
### Minimal reproduction project (MRP)
[project.zip](https://github.com/user-attachments/files/15776279/project.zip)
Contributor guide
Research direction
Start with the attached minimal reproduction project and reproduce the crash from the Signals and Groups tab by opening the signal popup and pressing Advanced. Then reload the project and verify the second crash path; the issue is done when both editor workflows open and remain usable without crashing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- game-dev, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100