TriggerRemoveAction vs TriggerClearActions

Witch one of these is making problems and why?

i guess both of em wont really cause any trouble if you used it correctly... is like comparing GroupRemoveUnit and GroupClear...

I've heard that TriggerClearActions causes problems... but I've only heard about it. No one has really explained to me why... meh... Just try it yourself and check for leaks.

Vexorian? heloooooooooo!

I am not sure if they would cause problems when I2H is totally out of the map. Then again I am not too sure TriggerClearActions actually fixes the memory leak, I just got myself used to exploit triggerconditions instead of actions for dynamic stuff...

When I tested it (quite a while ago), TriggerClearActions 'dereferences' the actions from the trigger, so they are no longer executed. However, the actions are not 'destroyed' and still take up memory. TriggerRemoveAction destroys the removed action.

(Basis: periodic timer creating a trigger, adding an action, calling one of the action removal functions and then destroying the trigger, nulled everything too. when using ClearActions, memory usage steadily increased, when using RemoveAction memory usage did not increase)

this is

RemoveUnit vs GroupRemoveUnit

clear actions useless function.