You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@groovy.apache.org by "Stefano Rocca (JIRA)" <ji...@apache.org> on 2016/07/13 10:00:25 UTC

[jira] [Created] (GROOVY-7884) GroovyScriptEngineImpl usage of CompilerConfiguration can lead to memory leaks

Stefano Rocca created GROOVY-7884:
-------------------------------------

             Summary: GroovyScriptEngineImpl usage of CompilerConfiguration can lead to memory leaks
                 Key: GROOVY-7884
                 URL: https://issues.apache.org/jira/browse/GROOVY-7884
             Project: Groovy
          Issue Type: Bug
            Reporter: Stefano Rocca


In the constructor of GroovyScriptEngineImpl the CompilerConfiguration is created each time, while it should use CompilerConfiguration.DEFAULT.

This can lead to memory leaks in environments where there is an high usage of GroovyScriptEngineImpl because CompilerConfiguration creates a PrintWriter on System.err (i.e. under the hood it creates a BufferedWriter with a default buffer of 8192 elements) when setting the field "output".
I have observed this behaviour using Apache Camel.
I don't know if all the GroovyScriptEngineImpl instances are legit or are themselves a leak: I will investigate on this later and report to the Apache Camel team.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)