Clearing Leaks

[Mechcash]

Hey guys Can somebody tell me how I clear leaks in following trigger:

I have no idea what to remove here, but Iam certain this trigger leaks.

Maybe someone could help out !

 

[IcemanBo]

Both actions leak one point. This will explain it:

Things That Leak
Memory Leaks

 

[MasterBlaster]

I'd say there's also a unit group leak in the condition.

@Mechcash read the guides above and try to figure it out by yourself, it will give you a lot more than anyone posting a solution for you. If you fail or have questions, come back and I'll help you out.

 

[Mechcash]

I'd say there's also a unit group leak in the condition.

@Mechcash read the guides above and try to figure it out by yourself, it will give you a lot more than anyone posting a solution for you. If you fail or have questions, come back and I'll help you out.

Thanks, will do

 

[FUJI]

You're leaking a unit group and a point and a region. They're not referenced hence they leak.
What you should do is to refer them first via variables, so open the variable creator (Ctrl + B)
And create a unit group variable, then a point variable, and lastly a region variable.

After this, set their appropriate values via GUI action 'Set Variable'.
Now you can use them as a reference and remove them after use.

You must set the region variable on initialization so we can reference it dynamically.
You must also put the condition below the actions so that you can use the newly created group variable.

Should be something like this:

• Initialization
  • Events
    • Map initialization
  • Conditions
  • Actions
    • -------- Setup Your Region Variable --------
    • Set MyRegion = (Entire map)

• Periodic
  • Events
    • Time - Every 2.00 seconds of game time
  • Conditions
  • Actions
    • -------- Setup Your Group Variable --------
    • Set MyGroup = (Units of type Footman)
    • -------- Use it as a reference in this condition --------
    • If (All Conditions are True) then do (Then Actions) else do (Else Actions)
      • If - Conditions
        • (Number of units in MyGroup) Less than or equal to 50
      • Then - Actions
        • -------- Setup Your Point Variable --------
        • Set MyPoint = (Random point in MyRegion)
        • -------- Use it as a reference in this function --------
        • Unit - Create 1 Footman for Player 1 (Red) at MyPoint facing Default building facing degrees
        • -------- Point Leak Removal --------
        • Custom script: call RemoveLocation(udg_MyPoint)
        • -------- - --------
        • -------- Setup Your Point Variable to a New Point --------
        • Set MyPoint = (Random point in MyRegion)
        • -------- Use it as a reference in this function --------
        • Unit - Order (Last created unit) to Patrol To MyPoint
        • -------- New Point Leak Removal --------
        • Custom script: call RemoveLocation(udg_MyPoint)
        • -------- - --------
      • Else - Actions
    • -------- - --------
    • -------- Group Leak Removal --------
    • Custom script: call DestroyGroup(udg_MyGroup)
    • -------- - --------
    • -------- If you're curious why I didn't destroyed entire rect then you shouldn't worry. --------
    • -------- We only leak that region once in the map initialization and using it dynamically. --------
    • -------- - --------

 

[Uncle]

@JAKEZINC
I'm pretty sure the Entire map region variable is unnecessary.

 

[FUJI]

We should be aware that 'Entire Region' function leaks.

 

[IcemanBo]

It can be tested if "(Entire map)" creates a new region each call, or always returns the same one by calling "GetHandleId()" function.

• Set Region = (Entire map)
• Custom script: call BJDebugMsg(I2S(GetHandleId(udg_Region)))
• Set Region = (Entire map)
• Custom script: call BJDebugMsg(I2S(GetHandleId(udg_Region)))

If it prints 2 different numbers it leaks