[Trigger] [GUI] Need help to fix memory leaks

[wannaknowledgemore]

Map Download
i don't know what function is leaked so can u take a look for me
if you think it's not worth the time then let me hire you(Anyway, I don't have a lot of money.)
but i hope it can fixed by GUI

 

[Pyrogasm]

You can, should, and eventually will have to learn how to do this yourself. Here is the best resource for learning: Things That Leak

You should not pay someone real money to fix leaks in your map; the skill is incredibly important and you will always have to be doing it.

 

[wannaknowledgemore]

You can, should, and eventually will have to learn how to do this yourself. Here is the best resource for learning: Things That Leak

You should not pay someone real money to fix leaks in your map; the skill is incredibly important and you will always have to be doing it.

i already did it everything
but i don't know is this function is blacklisted too?
if yes so what i need to use instead

Set Unit_Group[1] = (Units within 300.00 of Unit_Point[1] matching ...)
Unit Group - Pick every unit in Unit_Group[1] and do (Actions)
Loop - Actions

Unit Group - Remove all units from Unit_Group[1]
Custom script: call DestroyGroup(udg_Unit_Group[1])
Custom script: set udg_Unit_Group[1] = null

 

[Pyrogasm]

For your own future reference:

How To Post Your Trigger

TopHow To Post Your Triggers I've seen many and many members around the site who need help with their triggers but don't know how to post their triggers in a thread, especially the newcomers. Posting your triggers in a thread is very important when you're asking a help from other members to fix...

www.hiveworkshop.com

but i don't know is this function is blacklisted too?

I don't know what you mean by this. Which function? In the example trigger you showed you are doing everything correctly and will not leak anything. In fact, you are actually doing too much that you don't need to do.

• Remove all units from unit group is not necessary; the group does not have to be empty when it's destroyed. (Nothing will leak because of that.)
• Setting the variable = null is usuallynot needed because the variable is a global variable that will just get (re)assigned to something else eventually anyway.
  
  • You would need to do this for any variables that are local variables rather than globals, since those will never be used again after the end of the function where they cease to exist any more. Not nulling such variables is a "reference leak" rather than a "memory leak"; the object was destroyed properly but a variable still points to the destroyed object.
    
    
  • Any global variables that are made to function like local variables within a trigger/function will also need to be nulled before the end of the function where they cease to exist. This is sort of an advanced technique so you probably won't be using it, but just know that if you ever do use locally-shadowed globals you'll have to be careful about leaks with them.