11

I'm confused about this since I've seen several different comments. I'm reading a javascript book where it mentions that setting global variables to null is good practice (assuming there are no other references) and the GC reclaims memory for this variable on it's next sweep. I've seen other comments that say global variables are never disposed by the GC.

Also when programming javascript in a OOP structure, what happens if I have something like this (where game is in the global context):

var game = {};
game.level = 0;
game.hero = new hero();
//do stuff
game.hero = null;

Since hero lives inside an object which is stored in game, which is in a global context, If I set for instance hero to null, would this be disposed by the GC?

Felix Kling
  • 795,719
  • 175
  • 1,089
  • 1,143
user2000950
  • 511
  • 5
  • 14
  • 3
    You might want to read [What is JavaScript garbage collection?](http://stackoverflow.com/questions/864516/what-is-javascript-garbage-collection?rq=1). – Felix Kling May 28 '13 at 08:31

1 Answers1

17

Global variables are never disposed of by the GC in the sense that a global variable will still exist. Setting it to null will allow the memory that it references to be collected, however.

E.g.

Before:

global -> {nothingness}

After:

global -> var a -> object { foo: "bar" }

Set a to null:

global -> var a -> null

Here, the memory used by the object will be eligible for collection. The variable a still exists though, and it simply references null.

The statement that global variables are never collected is slightly misleading. It might be more accurate to say that any memory that is traceable back to the global context is not currently eligible for collection.

In answer to your question, yes - the hero object will be eligible for collection, because its indirect connection to the global context has been severed.

izb
  • 50,101
  • 39
  • 117
  • 168
  • 1
    Thanks that clarified it. I'm now wondering what would happen if you had 10000 variables in the global scope though... – user2000950 May 28 '13 at 09:55
  • 4
    Probably not very much that's bad. It's considered bad practice to pollute the global namespace with variables though. – izb May 28 '13 at 10:01