Thanks for the patch. It has been commited in the svn trunk branch
(2.1-SNAPSHOT).
Do you think there is any other precaution to take about this issue of
class reloading, for instance in the introspection package? Or would
there be any benefit to declare our own class loader to be able to
propagate some class reloading events to inner caches?
Claude
On 11/11/18 6:15 PM, Cédric Tabin wrote:
Hi,
I suggest to add a method to allow to clear the cache owned by each Type in
org.apache.velocity.util.DuckType.
This cache causes us some memory leak problems, because we are reloading
classes at runtime, causing it to grow indefinitely while preventing
"unloaded" classes to be garbage collected.
Since I'm not sure how to submit a patch to velocity, I submitted this PR
<https://github.com/apache/velocity-engine/pull/6> a while ago. It would be
great if a dev could check it out.
Actually, I wonder if this type of cache should be improved so it can be
configured by the developer ? It could be interesting at least to limit the
number of objects held by the cache.
Thanks & best regards,
Cédric
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org
For additional commands, e-mail: dev-h...@velocity.apache.org
