[JASS] Memory leakage

[sephiroth1234]

Hello. Could I ask something? Do JASS-type triggers still leaks memory even if without the line:call(udg_my_variable) ? Thanks in advance!!!

 

[Dynasti]

Leaks are the word used for Memory Leaks. Meaning that memory is unaccecable but stored. Thus meaning loss of speed etc.

When you don't remove a handle inside a variable or store a handle in a variable for later use, that handle will let go and will be in a such state where it cannot be retrived. If this happens alot it will lead to lagg. So Leak = Handles leaking out in to never be taken back.

All handles are auto destroyed uppon map quit.


So YES. JASS still leaks. Everything you do leaks, just remember to store->Destroy.

 

[sephiroth1234]

Leaks are the word used for Memory Leaks. Meaning that memory is unaccecable but stored. Thus meaning loss of speed etc.

When you don't remove a handle inside a variable or store a handle in a variable for later use, that handle will let go and will be in a such state where it cannot be retrived. If this happens alot it will lead to lagg. So Leak = Handles leaking out in to never be taken back.

All handles are auto destroyed uppon map quit.


So YES. JASS still leaks. Everything you do leaks, just remember to store->Destroy.

So I still must create a line : call(udg_my_variable) ??

 

[Pharaoh_]

Jass isn't the magic language that provides the greatest efficiency to the person, who uses it. It has flaws, like any other language and specially for the Warcraft III engine that is really unsupportive of many events the latest engines support, the flaws' number becomes bigger. So yes, like Dynasti said, GUI and Jass equally leak.

So I still must create a line : call(udg_my_variable) ??

Well, the "udg_", you won't need it for a Jass trigger (most likely). Udg_ is a prefix that defines the global substance of a variable. GUI only gives you the ability of creating global variables. They are the ones that cannot support MUI in its full potential. So, in Jass, you will instead use locals. if you use locals, it will not look like "udg_variable", it will be RemoveLocation(variable). Finally, it is not encouraged for a user to play around with locations in Jass, but GetUnitX() and GetUnitY(). Of course that depends on what you want.

 

[Dynasti]

Oh Seph, just FYI, every variable you make gets udg_YOURVARANME. udg = User Defined Global.

Where if you use vJass you can make your own globals without the udg.

 

[Mooglefrooglian]

Leaks are the word used for Memory Leaks. Meaning that memory is unaccecable but stored. Thus meaning loss of speed etc.

Not really. The WC3 engine can still remove them, it has a list of all the variables and deletes them properly when a game ends. Using memory leak really isn't the right word.

 

[Dynasti]

I didn't say it couldn't be removed. My point was when you first lose the handle id you're fucked. Unless you've got something magical up your sleeves

 

[sephiroth1234]

Thanks to all of you! Now I can create the triggers of my map 100% leakless.....

 

[Bribe]

Just make sure that if you use locals that have handles, such as local player p, local timer t, local unit u to set them all to null at the end of the function (or whenever you're done with them).

set p = null
set t = null
set u = null