Will this memory leak?

Help and Feedback Scripting Support
#1

Just a quick question which I kinda had a brainfart on.

If I clone a model (in this case a Player’s Character), and store it in a table, and then Model:Destroy() is called, will the table still hold a reference to this Model, and will it memory leak?

Thanks

1 Like
#2

No, :Destroy() erases all connections to it.

#3

It erases connections, yes, but I’m storing a reference to the model not a connection

I believe:Destroy() just parents to nil at the end? So isn’t the model technically in the game, and therefore there would still be a reference to it and it wouldn’t GC?

Table basically is:

{
    [Player.UserId] = Player.Character:Clone()
}

And then I plan to use the “FakeCharacter” and put it in the DebrisService to clean up if unused. Will a reference still exist, causing a memory leak?

#4

No, :Remove() just parents things to nil.

:Destroy() does destroy connections but it should also remove it from everything else entirely and completely disposes it. It shouldn’t cause a leak.

Wiki Reference: Instance | Documentation - Roblox Creator Hub

#5

Yes, the model will remain in memory unless the table is garbage collected or the model is removed from the table.

1 Like
#6

This is incorrect. All that Instance:Destroy does is set the parent of the instance to nil, lock the parent property, disconnect all connections and call Instance:Destroy on all children.

4 Likes
Is this a Memory Leak?
#7

GAH! Looks like I made a fatal mistake, sorry!

#8

Alright, thanks! I guess I’ll just use a delay and remove it myself instead of using DebrisService.

1 Like