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

Posted to notifications@groovy.apache.org by "Paul King (JIRA)" <ji...@apache.org> on 2017/02/01 23:19:03 UTC

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

     [ https://issues.apache.org/jira/browse/GROOVY-7884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul King closed GROOVY-7884.
-----------------------------

> 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
>    Affects Versions: 2.4.5
>            Reporter: Stefano Rocca
>            Assignee: John Wagenleitner
>             Fix For: 2.4.8
>
>
> 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.15#6346)