Affects Version/s: 2.0.12
Fix Version/s: 2.0.15
Number of attachments :
I also was under impression that WeakHashMap is good cache.
But it seems that it is not.
See attached screen shot from profiler.
As you can see, CompositeClassLoader is in memory, because TableLayout class is in memory.
Its method is in READ_PROPERTY_RESOLVER_CACHE and uses TableLayout as key (as I understand).
An entry in a <tt>WeakHashMap</tt> will automatically be removed when its key is no longer in ordinary use.
But Method is in value of entry, referenced using "strong" reference and Method also has strong reference on its Class.
So, this entry never will be removed.