Question about Memory Leak

[waves5217 (waves)]

Yes.

@MLH_gaming

If a connection keeps running and not disconnected, is it also a memory leak?

If the script “forgets” about the connection and moves on, doesn’t properly disconnect it or properly destroy the instance, it may be classified as a memory leak. In the example @Viscxse showed, the tool.Unequipped connection keeps being created on each equip. That’s most certainly a memory leak. By the time the tool is removed and destroyed, there may be dozens if not hundreds of useless unreachable connections.

@MLH_gaming

Also when a player leaves a game, why do we destroy the player object and not their character too?

I suggest taking a look at the tread I attached in my first post.

@MeerkatSpirit

A small discussion other devs and I had regarding player and character removal, espeically character.

Should you disconnect character connections when they die?

With my research, I noticed that “Destroyed” doesn’t fire when characters die and then respawn. Would this mean I should call a kind of disconnect function? For example: local Players = game:GetService("Players") local TempCon = nil Players.PlayerAdded:Connect(function(Plr) Plr.CharacterAdded:Connect(function(Char) TempCon = Char.ChildAdded:Connect(function() --Create any kind of event end) end) end) task.wait(5) --Player leaves before this continues print(TempCon.Connected) --Outpu…

MarmDev, sorry for another quote ping.