groovy-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GROOVY-7884) GroovyScriptEngineImpl usage of CompilerConfiguration can lead to memory leaks
Date Sun, 07 Aug 2016 03:00:25 GMT

    [ https://issues.apache.org/jira/browse/GROOVY-7884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15410805#comment-15410805
] 

ASF GitHub Bot commented on GROOVY-7884:
----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/groovy/pull/377


> 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
>
> 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)

Mime
View raw message