• 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!

Memory Leaks

Status
Not open for further replies.
Level 18
Joined
Jan 21, 2006
Messages
2,552
So what's the deal with memory leaks in StarCraft II? Did blizzard add some sort of garbage collection so we no longer have to destroy handles such as groups that are no longer being used?
 
From Blizzard:

-- Complex types and automatic deletion --

Many native types represent "complex" objects (i.e. larger than 4 bytes). The script language automatically keeps track of these objects and deletes them from memory when they are no longer used (that is, when nothing in the script references them any longer). The types which benefit from automatic deletion are:

abilcmd, bank, camerainfo, marker, order, playergroup, point, region, soundlink, string, text, timer, transmissionsource, unitfilter, unitgroup, unitref, waveinfo, wavetarget

Other object types must be explicitly destroyed with the appropriate native function when you are done using them.
 
Status
Not open for further replies.
Back
Top