• Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
  • Read Evilhog's interview with Gregory Alper, the original composer of the music for WarCraft: Orcs & Humans 🔗Click here to read the full interview.
  • The Hive's 22nd Icon Contest: Creep Abilities is now concluded, time to vote for your favourite set of icons! Click here to vote!
  • ✅ The POLL for Hive's Texturing Contest #34 is OPEN! Vote for the TOP 3 SKINS! 🔗Click here to cast your vote!
  • ✅ The POLL for Hive's Techtree Contest #20 is OPEN! Vote for the TOP 3 FACTIONS! 🔗Click here to cast your vote!

[Solved] What is the purpose of this action? +rep

Status
Not open for further replies.
Leaks should be taken seriously because it will be generated infinitely (well, until the system stops looping or stop its usage (for example leaking points that not been cleared))

While this trigger is a handle, which just not necessary to be destroyed but it can be destroyed

You can choose to destroy it or not, but leaks are a-must destroy
 
You can create new triggers during runtime, makes sense with the UnitWithinRange-event for example. So you would allocate a trigger for each unit but all the units might appear through other means. So you always store more stuff in memory. In contrast to a static leak, the max consumption is not limited and can therefore become a problem.
 
Status
Not open for further replies.
Back
Top