-
-
Notifications
You must be signed in to change notification settings - Fork 21.3k
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
Debugger dies when inspecting a recursive property #54622
Comments
I just noticed the same problem occur when creating a recursive meta property, even though neither the inspector tab nor the debugger tab draw the meta properties. Using the code bellow yields the same result as the code above, that is, the debugger dies. func _ready():
get_script().set_meta('this', self)
breakpoint |
Can confirm, I was about to report it, related to #51049. |
Can you reproduce it in 3.4? |
This: var a
func _ready():
a = self
breakpoint won't yield errors on 3.4. The debugger continues working normally. But this: func _ready():
get_script().set_meta('this', self)
breakpoint altough won't kill the debugger, will make the console continuously spam the message:
The debugger won't die and you are still able to step through code, but since the console will be spamming the error messages, the editor performance degrades drastically. |
It happens with this too. func _ready():
var d1 = {}
var a1 = []
d1["a"] = a1
a1.push_back(d1)
print(d1)
breakpoint Debugger dies in 3.4 lFC4Kv4iCg.mp4 |
Can confirm in 3.5.beta 7fcfde9. (Debugger crashes abruptly.) |
Similarly, in v4.1.1.stable.official [bd6af8e]
leads to... E 0:00:01:0832 Node2D.gd:4 @ _ready(): Potential infinite recursion detected. Bailing. |
Godot version
3.3.4 standard build for linux x64
System information
Ubuntu 21.04 x64
Issue description
The gdscript debugger dies when stopping on a breakpoint in a location where the inspector should draw a class property that contains a recursive value. Eg.: A reference to self.
Steps to reproduce
Minimal reproduction project
No response
The text was updated successfully, but these errors were encountered: