Leak Related

[akrep_ve_su]

Which of those following sitiautions cause leaks:
1-) An unit is stored in variable A. Then this unit dies or is removed via triggers.
Another trigger now issues an order with variable A (to non-existent unit) like:
- Order A to do something
Does this cause a leak (making an action where reference unit no longer exists)
P.S: Variable will be nullified to "no unit" sooner or later. What I am asking here is, when unit is stored in variable A and that unit no longer exists, making an action with that variable cause a leak, or not.

2-) Referring to a point using "Position of Unit X" cause leak?

3-) Referring to region with "Playable Map Area" cause leak?

4-) Does un-nullified item variables cause leak?

 

[Raven0]

1-) An unit is stored in variable A. Then this unit dies or is removed via triggers.
Another trigger now issues an order with variable A (to non-existent unit) like:
- Order A to do something
Does this cause a leak (making an action where reference unit no longer exists)

no, they probably have a null catch somewhere that will prevent the code from being processed if the value is null.

Referring to a point using "Position of Unit X" cause leak?

yes, the BJ that the GUI converts to creates a new location object that is never used again (location objects just store x and y values). You need to destroy the location afterwards or set the wantdestroy variable to true beforehand.

3-) Referring to region with "Playable Map Area" cause leak?

No, playable map area is a pre-defined rect variable (or region I can't remember) and nothing is created when you call this function, it just returns the variable value.

4-) Does un-nullified item variables cause leak?

Well it depends, if your never going to use that item variable again then yes. All a 'leak' is is some memory that has been allocated and is not being used. So if your never going to use that item variable again, then you should null it so the memory is wiped.

hope that all made some sense.

 

[akrep_ve_su]

They did =) Thank you =)
Edit:
Wait a minute. To prevent "position of unit" leak, how do I proceed?
I create a point variable and store "position of unit" inside that, then I destroy the variable. Is that it? =) Thanks in advance.

 

[akrep_ve_su]

I hate to double-post =) But can anyone confirm my previous post? I've already used that method.

 

[Dr Super Good]

You Remove the location the variable points to. In JASS you can not remove/detroy variables. Globals must be declared on map initialization in the global area of the script and will last until the game ends. Locals must be decleared at the start of a function and will last until the end of the function is reached.

An unit is stored in variable A. Then this unit dies or is removed via triggers.

Apparently, removing units via triggers is itself a leak. People say that it does not deallocate some of the memory and the handle ID the unit uses. Instead they advise making the unit explode on death and then killing it.

 

[Raven0]

Apparently, removing units via triggers is itself a leak. People say that it does not deallocate some of the memory and the handle ID the unit uses. Instead they advise making the unit explode on death and then killing it.

So the code for exploding units properly cleans up the memory but not the one for removing them? Brilliant...

I really hope Galaxy doesn't have these same problems

 

[Dr Super Good]

SC2E does not have any noticable leaks so far. Obviously you can still create your own leaks by doing stupid coding.

 

[defskull]

Set the unit exploding upon death + Remove OR Kill ?

 

[chobibo]

exploding upon death + Expiration Timer

 

[Bribe]

Expiration timer is good for most cases where you have a dummy caster, but a simple:

• Unit - Explode (Fart)

Is best if you know for sure you don't need that unit for even one more nanosecond.

 

[akrep_ve_su]

To prevent "position of unit" leak, how do I proceed?
I create a point variable and store "position of unit" inside that, then I destroy the variable. Is that it?

I was referring to GUI, not Jass.
Is this a proper method to prevent leaks from occourring:

• Set Position_Of_Unit[8] = (Position of (Ordered unit))
• Unit - Create 1 Classic Dummy for (Owner of (Ordered unit)) at Position_Of_Unit[8] facing (Facing of (Ordered unit)) degrees
• Unit - Add Attack Disable (out of ammo) to (Last created unit)
• Unit - Set level of Attack Disable (out of ammo) for (Last created unit) to 1
• Unit - Order (Last created unit) to Neutral Dark Ranger - Silence Position_Of_Unit[8]
• Custom script: call RemoveLocation (udg_Position_Of_Unit[8])

 

[Bribe]

You're removing the location properly, anything in particular you're concerned about?

 

[akrep_ve_su]

You're removing the location properly, anything in particular you're concerned about?

No, I needed someone to verify it =) Thanks.

 

[Dr Super Good]

then I destroy the variable. Is that it?

You can not destroy variables, only some types that handle variables point to.

 

[akrep_ve_su]

You can not destroy variables, only some types that handle variables point to.

I am not sure that I understand what you said =) But what I meant by "destroying the variable" was:

• Custom script: call RemoveLocation (udg_Position_Of_Unit[8])

If that prevents leak from occourring, that's all I care about =)

 

[defskull]

I think DSG is thinking WAYYY too far >.<
He's not gonna destroy variable, literally @.@

 

[Dr Super Good]

Hes destroying the object that the variable points to, the variable still exists.