Recursive references crash the game, prevent print() output and reaching breakpoints for whole code blocks.

[ScyDev]

I made a simple demo for this problem:
https://github.com/ScyDev/godot/tree/master/demos/crashes/recursive_reference_print_crash

---

Godot says "Process being debugged exited." before a breakpoint at the beginning of the loop is reached.

Update: It appears that the breakpoint is reached, because it influences the print() output. But I can't actually debug because of "Process being debugged exited".

godot -d says:

line index: 2 line: (crossed:False), (end:4.226463,-4.558409), (intersects:), (start:6.399961,-4.559154)
no intersect. adding line: (crossed:False), (end:4.226463,-4.558409), (intersects:), (start:6.399961,-4.559154)
mergedLines 1
indexOne 3 startIndex 2
line index: 3 line: (crossed:False), (end:4.225718,-6.731907), (intersects:), (start:4.226463,-4.558409)
no intersect. adding line: (crossed:False), (end:4.225718,-6.731907), (intersects:), (start:4.226463,-4.558409)
mergedLines 2
indexOne 4 startIndex 2
CLOSING CONNECTION
ERROR: set_stream_peer: Condition ' p_peer.is_null() ' is true.
   At: core/io/packet_peer.cpp:228.

[ScyDev]

The offending line seems to be:

print("line index: ",indexOne," line: ",currLine)

I kid you not. This crashes the game and prevents the debugger from ever reaching that code block.

These variations also do it:

        print("test "+str(currPoly))
        print("test ",currPoly[indexOne])
        print("test ",currLine)

[ScyDev]

Another day another insight:

The actual cause is that currLine is a dictionary which contains values that can reference back to currLine, thus creating a recursive reference. This crashes the game when trying to print() it.

[bojidar-bg]

Maybe we should just enforce some maximum depth when stringifying a dictionary?

[akien-mga]

First of all thank you for your report and sorry for the delay.

We released Godot 3.0 in January 2018 after 18 months of work, fixing many old issues either directly, or by obsoleting/replacing the features they were referring to.

We still have hundreds of issues whose relevance/reproducibility needs to be checked against the current stable version, and that's where you can help us.
Could you check if the issue that you described initially is still relevant/reproducible in Godot 3.0 or any newer version, and comment about it here?

For bug reports, please also make sure that the issue contains detailed steps to reproduce the bug and, if possible, a zipped project that can be used to reproduce it right away. This greatly speeds up debugging and bugfixing tasks for our contributors.

Our Bugsquad will review this issue more in-depth in 15 days, and potentially close it if its relevance could not be confirmed.

Thanks in advance.

Note: This message is being copy-pasted to many "stale" issues (90+ days without activity). It might happen that it is not meaningful for this specific issue or appears oblivious of the issue's context, if so please comment to notify the Bugsquad about it.

[Piet-G]

Seems to be the same issue as #8693

[Chaosus]

It seems to be, but #8693 was created far recently + the title here is better describe the problem.. instead I close #8693, and re-assign @reduz to this issue