[General] Something about memory leaks

[micca]

Well, I have this trigger. Do i need to always use "call RemoveLocation...", after "Point" variable, to remove leaks or it will overwrite itself every time it is used, so no memory leaks will occur?

Spoiler

• Reinforcements
  • Events
    • Time - Reinforcements expires
  • Conditions
  • Actions
    • For each (Integer A) from 1 to 4, do (Actions)
      • Loop - Actions
        • Set Point = (Random point in Reinforcements <gen>)
        • Unit - Create 1 Archer for Player 2 (Blue) at Point facing Default building facing degrees
        • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
          • If - Conditions
            • (Integer A) Less than or equal to 2
          • Then - Actions
            • Set Point = (Random point in Reinforcements <gen>)
            • Unit - Create 1 Huntress for Player 2 (Blue) at Point facing Default building facing degrees
          • Else - Actions
    • Set Group = (Units in Reinforcements <gen>)
    • Unit Group - Pick every unit in Group and do (Actions)
      • Loop - Actions
        • Set Point = (Random point in Reinforcements Dest <gen>)
        • Unit - Order (Picked unit) to Attack-Move To Point

 

[Chaosy]

Every time, I think.

 

[micca]

Ok, thank you.

 

[IcemanBo]

Read memory leak tutorial from my signature, it may help to understand why it should be removed each time. : )

 

[stonneash]

the value of the variable goes in the same place in memory, but the instsance point it is pulling the value from is unique and needs to be destroyed in an ideal memory management scenario.

 

[Dr Super Good]

All JASS variables are 32 bits. How complex objects like locations work is by allocating the object separately on the heap and then storing a reference to that object in the variable. The references come in the forms of handles, which are indices into a handle table which then contains the address of the actual object.

For all resources to be freed, the object must be destroyed by appropriate destructor and all variables referencing it must be assigned other values to allow the handle index to be recycled.

 

[stonneash]

Every time, I think.

the value of the variable goes in the same place in memory, but the instsance point it is pulling the value from is unique and needs to be destroyed in an ideal memory management scenario.

All JASS variables are 32 bits. How complex objects like locations work is by allocating the object separately on the heap and then storing a reference to that object in the variable. The references come in the forms of handles, which are indices into a handle table which then contains the address of the actual object.

For all resources to be freed, the object must be destroyed by appropriate destructor and all variables referencing it must be assigned other values to allow the handle index to be recycled.

I like the three different ways this was explained