Issue221738

Going by previous exchanges on the mailing lists,
this seems to be a known problem.

When a execfile() or eval() is repeatedly 
executed in a long running java process, a
new class gets created on every invocation.

This class does not get garbage collected
as long as the classloader which loaded it
is around.

This leads to a bloat of the java process
size (not in the heap, but in the code blocks).

Eval is kind of dispensable, but execfile is
not. One easy fix would be to cache the generated
class and reuse it the next time execfile is
called.

I can readily provide those patches. Is this
acceptable or is a different solution already
in the works ?
 

eval() and execfile() uses a new classloader for each invocation, and this classloader is kept around. So this should already work under most JVMs. It works for me.

Rather than having jython caching the generated class, it is usually better to do your own caching of the compiled code object by using compile() to create the code-object and the exec statement to run the code.