local variables leak?

local variables leak?

does the use of local variables causes memory leak if they get nullified after the use? I mean.. they stay somewhere in the memory just not pointing to anything.. or do they get erased away?

There seems to be a problem with that. Beats me why, but that useless pointing seems to consume memory. I think Cubasis or KaTTana proved that so it's better to nullify them. This must be one of Blizzard's fault.

~Daelin

Daelin - at last you came to this forum I noticed recently that Spells section is dying, I don't see Blade.dk, Nantuko_Husk, Leopard...

DaelinThere seems to be a problem with that. Beats me why, but that useless pointing seems to consume memory. I think Cubasis or KaTTana proved that so it's better to nullify them. This must be one of Blizzard's fault.

~Daelin

I read your tutorials about triggers and jass, and the others you linked in it.. thats why I'm asking about local variables.. it didn't get clear to me.. instead of using "pick every unit in region" im setting them to a variable, and in the end of the trigger I set it to null, but this makes my spell not MUI I think.. I was thinking of using local variables to solve this problem, but you said it leaks too.. what should I do? I tried to make every player to have his own TempVariable, but this takes too much memory too (though it seem to not leak).

Thanks for your help