[GROOVY-4698] Possible memory leak in Tomcat

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.7.8
• Fix Version/s: 2.4.6
• Component/s: groovy-runtime
• Environment: Groovy 1.7.8, Tomcat 6.0.28
• Assignee: John Wagenleitner
• Reporter: François-Xavier Guillemette
• Created: 25/Feb/11 15:39
• Updated: 22/Feb/16 20:48
• Resolved: 24/Jan/16 15:14

Description

Using Groovy 1.7.8 Groovlets on Tomcat 6.0.28 yields the following in the log files:

The web application [...] created a ThreadLocal with key of type [null] (value [groovy.util.GroovyScriptEngine$2@68aed52c]) and a value of type [org.codehaus.groovy.tools.gse.StringSetMap] (value [{}]) but failed to remove it when the web application was stopped. This is very likely to create a memory leak.

Issue Links

• is related to: GROOVY-4177 Groovy categories cause tomcat memory leak and prevent tomcat shutting down