Table marshalling does not detect circular references

[Quenty]

ROBLOX will crash if you try to send a table that points to itself through the BindableEvent. I suspect it's because of the ROBLOX serializer, no other reason would force a recursion through a table as far as I can tell.

Example code that results in the crash, yes, parts of it are generic, but I don't want to share the 20,000 lines of code.

The above code creates a table that refers to itself. The below code contains a signal event that pushes through using the BindableEvent object, which serializes ROBLOX tables (as far as I can tell). This results in an infinite loop, since the serilizer doesn't have pointers, and you get a beautiful crash.

The beautiful output;

Which is really hard to debug.

[Quenty]

ROBLOX has just made it error when circular references have been identified.

[Anaminus]

Is it fixed on the client? It still crashes in studio.

[Quenty]

I was pretty sure it was fixed. I think we better reopen if it is crashing for you.

[matthewdean]

@Quenty: Please refrain from posting huge chunks of code which don't even reproduce the problem. Just include something like this:

local t = {}
t[1] = t
Instance.new("BindableFunction"):Invoke(t) -- studio crashes

That way we can run the snippet to see if the problem has been fixed.

[Quenty]

@matthewdean Will do.

[matthewdean]

This has been fixed:

local t = {}
t[1] = t
Instance.new("BindableFunction"):Invoke(t)
--> error: tables cannot be cyclic