some thoughts on ClassValue
John Rose
john.r.rose at oracle.com
Sat Apr 27 14:26:56 PDT 2013
On Apr 27, 2013, at 2:13 PM, Jochen Theodorou <blackdrag at gmx.org> wrote:
> per application and imagine the
> application is loaded and unloaded several times... a meta class is a
> large structure with a lot of objects. I could very easily write a
> Groovy script for such an environment that will eat up all the memory in
> this new meta class system while currently it should run with some big
> gc runs, but still run endlessly.
Each instance of the Groovy runtime will use a distinct ClassValue instance.
If the ClassValue instance goes dead, then all the values (for each class) bound using that instance should go dead also.
If they don't it's a bug.
— John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.openjdk.java.net/pipermail/mlvm-dev/attachments/20130427/f9fa825f/attachment.html
More information about the mlvm-dev
mailing list