[General] Leak ?

[defskull]

Will this leak ?

• Custom script: Set TempLoc = SomePoint
• -------- DO SOMETHING WITH THE SomePoint --------
• Custom script: Set TempLoc = SomePoint2
• -------- DO SOMETHING WITH THE SomePoint2 --------
• Custom script: Set TempLoc = SomePoint3
• -------- DO SOMETHING WITH THE SomePoint3 --------
• Custom script: call RemoveLocation(udg_TempLoc)

Basically, does overwriting Point, causes leak (even though we properly clean it in the end) ?

 

[edo494]

Yes.

This is because variable is only like a bucket, and you fill that bucket with liquids, which are the objects created.

However, when you do something like RemoveLocation, what you basically do is you look into the bucket, and what is currently in the bucket gets removed. But when you assign to the variable some different location, what you do is basically you take the bucket, you say "I dont need this anymore" and you pour the liquid inside the bucket on the ground, and fill it with another. But you cant destroy something that is not in bucket(or hashtable, gamecache).

So if SomePoint and SomePoint2 are created, not just referenced(like loaded from hashtable), then yes, you leak 2 points, because they are still in the memory, but you dont have anyone pointing their finger on them(all variables except real, boolean and integer are basically pointers)

 

[IcemanBo]

I assume SomePoint and SomePoint2 not to be variables of type location, so yes, it leaks because you can't refer anymore to the storage.

As general rule, ensure to remove the object before you store new data to the variable. Ensure to null a variable (abstract types) if you won't use it anymore.

Edit: Edo won.

 

[defskull]

Thanks guys