Memory Leak Clarification

Okay, so referencing a location such as "Center of Region" leaks. The typical solution to this is:
From start to finish, that code fires about 2708 times, and 404 of those executions happen simultaneously. Assigning that variable and removing it everytime when it fires seems a bit excessive, so what's the best way to handle the leak? Would assigning that location variable at the start of the map then referencing only to that variable without clearing it still leak?

Learn JASS so you only have to use Loc's for terrain Z. I can't say more atm, but I'll edit the post later.

You could perhaps leak that one location ...but that doesnt matter at all ..its ..dunno ...4bytes ?

Wouldn't it leak every time that trigger fires?

I'm not sure it's "excessive". That seems like proper protocol for Localizing the global variable, so... What's the beef?

Assigning a variable and removing it 400 times instantaneously is what seems excessive.

hmm ..wont do any harm ...only thing could be thread crash due to op limit hit... but i think that may take more than 400 times that shit ..to reach the limit

Well, it all depends on how "instantaneously" it really is.

AFAIK, a trigger runs through a whole time, with no interruptions. So even if it does it 400 times consecutively, that's cool; it's what it's meant to do.

Also, what in the world is doing that to a location so many times??

If you can still access and are still using the location, it is not actually leaked. Cached would be a better word.

I'm curious to know what exactly that's for as well o.o

Let me assure you that the unit order is by far the most expensive call there. The assignment and cleanup are jokes in comparison.