Is removing units from group enough to solve memory leaks?

[DrunkenDirt]

What title says, does a system like the one below prevent leaking, or do I need to destroy the group with a custom script? Haven't been able to find a clear answer.

• Untitled Trigger 004
  • Events
  • Conditions
  • Actions
    • Set VariableSet GroupUnit_Temp1 = (Units of type Footman)
    • Unit Group - Pick every unit in GroupUnit_Temp1 and do (Actions)
      • Loop - Actions
        • Unit Group - Remove (Picked unit) from GroupUnit_Temp1.

To be clear, I know how to prevent group leaking by destroying the group with custom scripts, I'm wondering if the above works as well.

 

[Peacehagen]

Im pretty sure you have to destroy it. An empty unit group will also leak.
Might be wrong though so better wait for more replies

 

[Strydhaizer]

You're not really removing the unit group, you're just removing the units from the unit group, you still have to destroy it, just make sure the unit group you created is temporary and will not be used again.

 

[Pyrogasm]

To be clear: a group does not have to be empty when you destroy it. There will no ill effects from doing so.

 

[nvhazard]

I think calling

set bj_wantDestroyGroup = true

before creating a group should be enough, is this true?