You seem to have a good understanding of storage management in HotSpot. To get more specific details, it's a good idea to go to the horse's mouth - in this case, the HotSpot developers. This page is a description of the storage management system.
In situations where I want to find out what code I am trying to find and find the code and read it. In this case, we can find an implementation of the KlassKlass class here . This does not seem to add additional information on top of Klass - which is very interesting to see. Note that KlassKlass continues with Klass .
So why do we need this? Well, we can highlight the Klass hierarchy of a particular program as a tree, where one Klass describes another. Everything needs a description, but we cannot continue it like this forever, we need to find a fixed point where the thing that we use to describe something is itself - so we can stop!
So, in a resume, KlassKlass does nothing more useful than the existing one. It must exist, but its existence is reasonably uninteresting.
selig Jun 11 '13 at 23:10 2013-06-11 23:10
source share