Re: Leaking LambdaForm classes?

2017-01-06 Thread Charles Oliver Nutter
On Fri, Jan 6, 2017 at 2:59 PM, Vladimir Ivanov < vladimir.x.iva...@oracle.com> wrote: > LambdaForm caches deliberately keep LF instances using SoftReferences. > > The motivation is: > (1) LFs are heavily shared; > (2) LFs are expensive to construct (LF interpreter is turned off by > default

Re: Leaking LambdaForm classes?

2017-01-06 Thread Vladimir Ivanov
LambdaForm caches deliberately keep LF instances using SoftReferences. The motivation is: (1) LFs are heavily shared; (2) LFs are expensive to construct (LF interpreter is turned off by default now); it involves the following steps: new LF instance + compile to bytecode + class loading.

Re: Leaking LambdaForm classes?

2017-01-06 Thread John Rose
Could be LF caching gone rogue. Does the user create many LF shapes, e.g. one per datum? – John > On Jan 6, 2017, at 9:32 AM, Charles Oliver Nutter wrote: > > Anyone else encountered this? > > https://github.com/jruby/jruby/issues/4391 > > We have a user reporting

Leaking LambdaForm classes?

2017-01-06 Thread Charles Oliver Nutter
Anyone else encountered this? https://github.com/jruby/jruby/issues/4391 We have a user reporting metaspace getting filled up with LambdaForm classes that have no instances. I would not expect this to happen given that they're generated via AnonymousClassloader and we would need to hold a