Difference between revisions of "Legacy:Garbage Collection"

Latest revision as of 16:29, 5 January 2013

Garbage is an unused part or element of code to which memory was allocated, (some resource of a program, or process), and, subsequently, has no pointers to it or has had its references destroyed. Garbage does no damage to a program initially, but it will gradually monopolize all available memory and the system will tend to run slower and slower and eventually fail or crash. Garbage collection involves running a program periodically that identifies and collects all garbage and frees memory (for more garbage). All objects and actors in Unreal are garbage-collected using a tree-following garbage collector similar to that of the Java VM.

Garbage Collection in Unreal essentially consists of serializing all Objects in the game (that includes Actors too, of course), and then deleting anything that doesn't end up being serialized. Full Garbage Collection in Unreal occurs automatically at a level change, or can be forced with a console command. Generally since most Objects are relatively small, the overhead for having the Objects stay around in memory is also relatively small (with the gluttonous UWindowWindow being an exception of course).

Related Topics[edit]

• Garbage collection / memory monitoring console commands
• Destroying Objects
• Wikipedia:Automatic garbage collection
• Wormbo explain somethink about garbage collection