[GROOVY-7884] GroovyScriptEngineImpl usage of CompilerConfiguration can lead to memory leaks

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.5
• Fix Version/s: 2.4.8
• Assignee: John Wagenleitner
• Reporter: Stefano Rocca
• Created: 13/Jul/16 09:59
• Updated: 01/Feb/17 23:18
• Resolved: 07/Aug/16 03:14

Description

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.

Issue Links

• links to: GitHub Pull Request #377