Leak problem?

[Lightskin]

Hello everyone, I was editting my map and I saw a note I left myself some time ago, but I cannot remember why. Probably should pay attention and ask; why is this leaking? in case I was right haha

• Rune to Stone
  • Events
    • Unit - A unit Finishes an upgrade
  • Conditions
    • (Unit-type of (Triggering unit)) Equal to Meeting Stone
  • Actions
    • -------- THIS LEAKS --------
    • Unit - Create 3 Gatherer (first) for (Owner of (Triggering unit)) at (Position of (Triggering unit)) facing (Random angle) degrees

 

[KILLCIDE]

Position of (Triggering unit) creates an object that will occupy a space in memory. When you can't refer to that specific object anymore, that is called a leak.

I recommend taking a read on IcemanBo's Memory Leaks tutorial. He goes in depth of what a memory leak, all the different types of objects that leak, and how to properly remove them.

 

[Lightskin]

Great tutorial! thanks for enlightening me. So if i understood correctly, i just fixed it; right?

• Rune to Prehistory
  • Events
    • Unit - A unit Finishes an upgrade
  • Conditions
    • (Unit-type of (Triggering unit)) Equal to Meeting Stone
  • Actions
    • Set location = (Position of (Triggering unit))
    • Unit - Create 3 Gatherer (first) for (Owner of (Triggering unit)) at location facing (Random angle) degrees
    • Custom script: call RemoveLocation(udg_location)

 

[KILLCIDE]

Yep that is right.

If you want a tutorial that just shows what leaks and how to remove them, check out Ralle's Things That Leak tutorial.

 

[Lightskin]

thank you very much ^^ +rep