• 💀 Happy Halloween! 💀 It's time to vote for the best terrain! Check out the entries to Hive's HD Terrain Contest #2 - Vampire Folklore.❗️Poll closes on November 14, 2023. 🔗Click here to cast your vote!
  • 🏆 Texturing Contest #33 is OPEN! Contestants must re-texture a SD unit model found in-game (Warcraft 3 Classic), recreating the unit into a peaceful NPC version. 🔗Click here to enter!
  • 🏆 HD Level Design Contest #1 is OPEN! Contestants must create a maze with at least one entry point, and at least one exit point. The map should be made in HD mode, and should not be openable in SD. Only custom models from Hive's HD model and texture sections are allowed. The only exceptions are DNC models and omnilights. This is mainly a visual and design oriented contest, not technical. The UI and video walkthrough rules are there to give everyone an equal shot at victory by standardizing how viewers see the terrain. 🔗Click here to enter!

Are Reals leaking?

Not open for further replies.
Level 31
Jul 10, 2007
Here is a great rule for leaks.

If you create it, it will stay until it is removed. For example, creating a group or a unit. If you no longer reference something and you don't remove it, that's a leak (it's sitting around in your map). For example, enumerating through a group and then never destroying that group.

If you reference something that is created and can be destroyed, that reference (the pointer) will leak. If it didn't leak, there would be a possibility of a unit pointer referencing a timer-

local unit u=CreateUnit()
local timer t
call RemoveUnit(u)
set t=CreateTimer()
//u would reference t if pointers were recycled regardless of what was referencing them

So yes, you have to null your pointers, otherwise they are never reused and the handle table (a hashtable) gets cluttered.
Not open for further replies.