What is the garbage collector in Java?

by

The garbage collector is a program which runs on the Java Virtual Machine which gets rid of objects which are not being used by a Java application anymore. It is a form of automatic memory management.

When a typical Java application is running, it is creating new objects, such as Strings and Files, but after a certain time, those objects are not used anymore. For example, take a look at the following code:

for (File f : files) {
    String s = f.getName();
}

In the above code, the String s is being created on each iteration of the for loop. This means that in every iteration, a little bit of memory is being allocated to make a String object.

Going back to the code, we can see that once a single iteration is executed, in the next iteration, the String object that was created in the previous iteration is not being used anymore — that object is now considered “garbage”.

Eventually, we’ll start getting a lot of garbage, and memory will be used for objects which aren’t being used anymore. If this keeps going on, eventually the Java Virtual Machine will run out of space to make new objects.

That’s where the garbage collector steps in.

The garbage collector will look for objects which aren’t being used anymore, and gets rid of them, freeing up the memory so other new objects can use that piece of memory.

In Java, memory management is taken care of by the garbage collector, but in other languages such as C, one needs to perform memory management on their own using functions such as malloc and free. Memory management is one of those things which are easy to make mistakes, which can lead to what are called memory leaks — places where memory is not reclaimed when they are not in use anymore.

Automatic memory management schemes like garbage collection makes it so the programmer does not have to worry so much about memory management issues, so he or she can focus more on developing the applications they need to develop.

More Related Contents:

  1. Error java.lang.OutOfMemoryError: GC overhead limit exceeded
  2. When does System.gc() do something?
  3. finalize() called on strongly reachable objects in Java 8
  4. Can java finalize an object when it is still in scope?
  5. Are static fields open for garbage collection?
  6. Does setting Java objects to null do anything anymore?
  7. Java Garbage Collection Log messages
  8. Java garbage collector – When does it collect?
  9. GC overhead limit exceeded
  10. Garbage collection on a local variable
  11. Android – Activity Constructor vs onCreate
  12. Analyzing gc logs
  13. Which loop has better performance? Why?
  14. When and how are classes garbage collected in Java?
  15. Garbage collection behaviour for String.intern()
  16. Empty an ArrayList or just create a new one and let the old one be garbage collected? [duplicate]
  17. Thread Caching and Java Memory model
  18. Does using final for variables in Java improve garbage collection?
  19. Will .hashcode() return a different int due to compaction of tenure space?
  20. Java GC safepoint
  21. Calling System.gc( ) explicitly?
  22. Does the garbage collector work on static variables or methods in java?
  23. Reference to object during finalize
  24. How do you Force Garbage Collection from the Shell?
  25. “Island of isolation” of Garbage Collection
  26. When would the garbage collector erase an instance of an object that uses Singleton pattern?
  27. Java and manually executing finalize
  28. Default garbage collector for Java 8
  29. Measuring time spent on GC
  30. When does Java’s garbage collection free a memory allocation?

Leave a Comment