Let us take a look at another demo application that allocates a lot of objects, which are successfully reclaimed during minor garbage collections. Bearing in mind the trick of altering the tenuring threshold from the previous section on promotion rate, we could run this application with -Xmx24m -XX:NewSize=16m -XX:MaxTenuringThreshold=1 and see this in GC logs:
2.330: [GC (Allocation Failure) 20933K->8229K(22528K), 0.0033848 secs] 2.335: [GC (Allocation Failure) 20517K->7813K(22528K), 0.0022426 secs] 2.339: [GC (Allocation Failure) 20101K->7429K(22528K), 0.0010920 secs] 2.341: [GC (Allocation Failure) 19717K->9157K(22528K), 0.0056285 secs] 2.348: [GC (Allocation Failure) 21445K->8997K(22528K), 0.0041313 secs] 2.354: [GC (Allocation Failure) 21285K->8581K(22528K), 0.0033737 secs] 2.359: [GC (Allocation Failure) 20869K->8197K(22528K), 0.0023407 secs] 2.362: [GC (Allocation Failure) 20485K->7845K(22528K), 0.0011553 secs] 2.365: [GC (Allocation Failure) 20133K->9501K(22528K), 0.0060705 secs] 2.371: [Full GC (Ergonomics) 9501K->2987K(22528K), 0.0171452 secs]
Full collections are quite rare in this case. However, if the application also starts creating weak references (-Dweak.refs=true) to these created objects, the situation may change drastically. There may be many reasons to do this, starting from using the object as keys in a weak hash map and ending with allocation profiling. In any case, making use of weak references here may lead to this:
2.059: [Full GC (Ergonomics) 20365K->19611K(22528K), 0.0654090 secs] 2.125: [Full GC (Ergonomics) 20365K->19711K(22528K), 0.0707499 secs] 2.196: [Full GC (Ergonomics) 20365K->19798K(22528K), 0.0717052 secs] 2.268: [Full GC (Ergonomics) 20365K->19873K(22528K), 0.0686290 secs] 2.337: [Full GC (Ergonomics) 20365K->19939K(22528K), 0.0702009 secs] 2.407: [Full GC (Ergonomics) 20365K->19995K(22528K), 0.0694095 secs]
As we can see, there are now many full collections, and the duration of the collections is an order of magnitude longer! Another case of premature promotion, but this time a tad trickier. The root cause, of course, lies with the weak references. Before we added them, the objects created by the application were dying just before being promoted to the old generation. But with the addition, they are now sticking around for an extra GC round so that the appropriate cleanup can be done on them. Like before, a simple solution would be to increase the size of the young generation by specifying -Xmx64m -XX:NewSize=32m:
2.328: [GC (Allocation Failure) 38940K->13596K(61440K), 0.0012818 secs] 2.332: [GC (Allocation Failure) 38172K->14812K(61440K), 0.0060333 secs] 2.341: [GC (Allocation Failure) 39388K->13948K(61440K), 0.0029427 secs] 2.347: [GC (Allocation Failure) 38524K->15228K(61440K), 0.0101199 secs] 2.361: [GC (Allocation Failure) 39804K->14428K(61440K), 0.0040940 secs] 2.368: [GC (Allocation Failure) 39004K->13532K(61440K), 0.0012451 secs]
The objects are now once again reclaimed during minor garbage collection.
The situation is even worse when soft references are used as seen in the next demo application. The softly-reachable objects are not reclaimed until the application risks getting an OutOfMemoryError. Replacing weak references with soft references in the demo application immediately surfaces many more Full GC events:
2.162: [Full GC (Ergonomics) 31561K->12865K(61440K), 0.0181392 secs] 2.184: [GC (Allocation Failure) 37441K->17585K(61440K), 0.0024479 secs] 2.189: [GC (Allocation Failure) 42161K->27033K(61440K), 0.0061485 secs] 2.195: [Full GC (Ergonomics) 27033K->14385K(61440K), 0.0228773 secs] 2.221: [GC (Allocation Failure) 38961K->20633K(61440K), 0.0030729 secs] 2.227: [GC (Allocation Failure) 45209K->31609K(61440K), 0.0069772 secs] 2.234: [Full GC (Ergonomics) 31609K->15905K(61440K), 0.0257689 secs]
And the king here is the phantom reference as seen in the third demo application. Running the demo with the same sets of parameters as before would give us results that are pretty similar as the results in the case with weak references. The number of full GC pauses would, in fact, be much smaller because of the difference in the finalization described in the beginning of this section.
However, adding one flag that disables phantom reference clearing (-Dno.ref.clearing=true) would quickly give us this:
4.180: [Full GC (Ergonomics) 57343K->57087K(61440K), 0.0879851 secs] 4.269: [Full GC (Ergonomics) 57089K->57088K(61440K), 0.0973912 secs] 4.366: [Full GC (Ergonomics) 57091K->57089K(61440K), 0.0948099 secs] Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
One must exercise extreme caution when using phantom references and always clear up the phantom reachable objects in a timely manner. Failing to do so will likely end up with an OutOfMemoryError. And trust us when we say that it is quite easy to fail at this: one unexpected exception in the thread that processes the reference queue, and you will have a dead application at your hand.