On Tue, Jan 30, 2018 at 6:10 PM, Sebastien <[email protected]> wrote:

> Haha, but I'm sure something has been fixed in the meanwhile just to make
> me lie! :p
> But still, the "win a beer" challenge is kept opened :)
>
> So here are the dump sizes as of today:
>
> jan. 23 19:41 - tomcat_heapdump_20180123.hprof - 65 MB
> jan. 25 15:05 - tomcat_heapdump_20180125.hprof - 120.9 MB
> jan. 30 17:24 - tomcat_heapdump_20180130.hprof - 116.2 MB
>
> On the latest dump, the 2 biggest objects (by retained size) are :
>
> Class Name / Retained Size
> org.apache.wicket.settings.ResourceSettings#1 / 5,741,149
> org.apache.wicket.core.util.resource.locator.caching.
> CachingResourceStreamLocator#1
> / 5,450,900
>
> Don't know what it does mean actually...
>

Both classes keep some caches related to resource references.
5MB is not a small number but knowing that Wicket jQuery UI comes with many
Kendo static resources I guess it is normal.
You can check what is inside these classes with Eclipse Memory Analyzer.


>
> Thanks & best regards,
> Sebastien.
>
> On Tue, Jan 30, 2018 at 5:21 PM, Andrea Del Bene <[email protected]>
> wrote:
>
> > It's really disappointing when things don't go wrong :-D
> >
>

Reply via email to