[Trigger] problem with terrain

[sangir]

First off i know the easyest way to fix this problem would be regions in but that is a pain in the _ _ _

the current trigger im trying to fix while still being lazy is leaking and ive tried leak check and it didnt work. so heres the trigg see what you guys can find

 

[RED BARON]

Well PurplePoot explained it the right way, so no need to say this. Still what is said aboved in both post is what I meant...

 

[paskovich]

It's the group that still leaks.

 

[RED BARON]

Well thats the easy way to say it

 

[PurplePoot]

You leaked the Unit Group as paskovitch said, plus you never destroy 'Snow'

Well you trigger happens: 100 times on 1 second.. thats 6000 times on 1 min. And for every one of those 6000times it has to set 3 variables, and define terrian the unit is walking on..for every unit in map.. lets just say you have about 50 units in map.. that means it has to do it: 300000 times per min, well that is why it leaks.
Maybe just make some regions over the snow/ice parts (also those places where there aint snow but just is close to the snow so you can split the map in lets say about 8 regions... then it would only have to do: 37500 times per min. But damn then it would be eight times the 37500 = the same as before... realy the only sollution I can think off would be the "boring job to make lets say max 7 regions for the places where there are snow or try to get some jass minded to solve it for you...

Leaks are permanent losses of memory. Warcraft can handle hundreds of times as many operations at this speed without lag on a decent computer. Thus, even though they're not leaks, a tiny trigger such as this one should cause no lag problems whatsoever.

Ever seen a JASS spell that runs with a projectile, or a knockback? That's running WAY more data and calculations at an interval of somewhere between .0035 to .04 seconds.

 

[sangir]

so how do i fix it

 

[PurplePoot]

Whoops, noticed that you used a variable for the group.

Well, the leak directly in that trigger can be fixed by putting

Custom script: call RemoveLocation( udg_Snow )

right after the if-statement