point leak in hash

[Caleb]

what is the custom script that i need to destroy it?

 

[PurgeandFire]

• Custom script: call RemoveLocation(udg_MyPointVariable)

 

[Caleb]

• Custom script: call RemoveLocation(udg_MyPointVariable)

i know that. but i am storing handle inside hash, not variable.

btw, look at this trigger, will this leak?

• Untitled Trigger 003
  • Events
  • Conditions
  • Actions
    • Hashtable - Save Handle Of(Position of (Random unit from (Units in (Playable map area)))) as 1 of (Key point) in myHash
    • Wait 2.00 seconds
    • Custom script: call RemoveLocation(GetUnitLoc(GroupPickRandomUnit(GetUnitsInRectAll(GetPlayableMapRect())))

)

 

[mckill2009]

you cant do that coz it leaks, store it in a variable first and do the remove thing that purge said...

 

[Caleb]

you cant do that coz it leaks, store it in a variable first and do the remove thing that purge said...

ok i'll do it. btw, all kinds of handles do leaks right? so how to destroy a unit handle that has been stored in hash or a variable?

 

[mckill2009]

not all handles leak, so you dont need to destroy units/integers/strings/reals...but you should destroy points/lightning/sound etc...

you can also flush/clear the hashtable child so that it will clear any data for that type of ID...

 

[Garfield1337]

not all handles leak, so you dont need to destroy units/integers/strings/reals...but you should destroy points/lightning/sound etc...

you can also flush/clear the hashtable child so that it will clear any data for that type of ID...

Integers, strings and reals aren't handles.

@Caleb, What you need to do is, load the location from hashtable and assign it to a variable and then destroy it before flushing the child hashtable. Hashtable only points the location handle, flushing the child hash will remove the pointer and cause a leak which is why you need to remove the location first.

 

[Caleb]

okay