Java garbage collector – When does it collect?

by

It runs when it determines that it is time to run. A common strategy in generational garbage collectors is to run the collector when an allocation of generation-0 memory fails. That is, every time you allocate a small block of memory (big blocks are typically placed directly into “older” generations), the system checks whether there’s enough free space in the gen-0 heap, and if there isn’t, it runs the GC to free up space for the allocation to succeed.
Old data is then moved to the gen-1 heap, and when space runs out there, the GC runs a collection on that, upgrading the data which has been there longest to the gen-2 heap, and so on. So the GC doesn’t just “run”. It might run on the gen-0 heap only (and most collections will do just that), or it might check every generation if it really has to free up a lot of memory (which is only necessary fairly rarely).

But this is far from the only strategy. A concurrent GC runs in the background, cleaning up while the program is running. Some GC’s might run as part of every memory allocation. An incremental collector might do that, scanning a few objects at every memory allocation.

The entire point in a garbage collector is that it should just do its thing without requiring any input from the user. So in general, you can’t, and shouldn’t, predict when it’ll run.

I believe Suns JVM gained a generational GC not too long ago (v1.6 maybe? I haven’t coded Java for ages, so not sure on this, but I remember being surprised not too long ago, when one of the selling points for the new version was “a generational GC”. Not least because .NET has had one since day 1.)

Other JVM’s are of course free to pick whichever strategy they like.

EDIT: The above part about Java and generational GC is not true. See below for more details:

The 1.0 and 1.1 Virtual Machines used a mark-sweep collector, which could fragment the heap after a garbage collection. Starting with Java 1.2, the Virtual Machines switched to a generational collector, which has a much better defragmentation behavior (see Java theory and practice: Garbage collection and performance).

So Java actually has a generational GC for ages. What’s new in Java 6 is the Garbage-First garbage collector (G1) that is available in Java 6u14. According to the article claiming the release in 1.6.0_14: It is not enabled by default. The parallel collector is still the default GC and is the most efficient GC for common household usage. G1 is meant to be an alternative for the concurrent collector. It is designed to be more predictable and enable fast allocation with memory regions design.

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. What is the garbage collector in Java?
  5. Java heap terminology: young, old and permanent generations?
  6. How to free memory in Java?
  7. Java 7 (JDK 7) garbage collection and documentation on G1
  8. Does setting Java objects to null do anything anymore?
  9. Java Garbage Collection Log messages
  10. GC overhead limit exceeded
  11. Android – Activity Constructor vs onCreate
  12. Analyzing gc logs
  13. Which loop has better performance? Why?
  14. Garbage collection behaviour for String.intern()
  15. Empty an ArrayList or just create a new one and let the old one be garbage collected? [duplicate]
  16. Java still uses system memory after deallocation of objects and garbage collection
  17. Does using final for variables in Java improve garbage collection?
  18. Will .hashcode() return a different int due to compaction of tenure space?
  19. Java GC safepoint
  20. Calling System.gc( ) explicitly?
  21. Does the garbage collector work on static variables or methods in java?
  22. Reference to object during finalize
  23. “Island of isolation” of Garbage Collection
  24. When would the garbage collector erase an instance of an object that uses Singleton pattern?
  25. Java and manually executing finalize
  26. Java GC (Allocation Failure)
  27. How to reduce java concurrent mode failure and excessive gc
  28. Static references are cleared–does Android unload classes at runtime if unused?
  29. How to read a verbose:GC output?
  30. What GC parameters is a JVM running with?

Leave a Comment