| From | Sent On | Attachments |
|---|---|---|
| asperkins | Oct 22, 2008 10:36 am | |
| Jochen Theodorou | Oct 22, 2008 11:11 am | |
| asperkins | Oct 22, 2008 11:25 am | |
| Jochen Theodorou | Oct 22, 2008 11:39 am | |
| Robert Fischer | Oct 22, 2008 11:43 am | |
| asperkins | Oct 22, 2008 11:53 am | |
| asperkins | Oct 22, 2008 11:58 am | |
| Graeme Rocher | Oct 23, 2008 12:12 am | |
| Tom Nichols | Oct 23, 2008 6:15 am | |
| Jochen Theodorou | Oct 23, 2008 6:35 am | |
| asperkins | Jan 22, 2009 7:57 am | |
| John Prystash | Jan 22, 2009 8:09 am | |
| asperkins | Jan 28, 2009 7:33 am | |
| asperkins | Jan 28, 2009 8:31 am | |
| Jochen Theodorou | Jan 28, 2009 8:59 am | |
| asperkins | Jan 28, 2009 9:15 am |
| Subject: | [groovy-user] ConfigSlurper / GroovyClassLoader memory leak | |
|---|---|---|
| From: | asperkins (tony...@travelocity.com) | |
| Date: | Oct 22, 2008 10:36:03 am | |
| List: | org.codehaus.groovy.user | |
The following snippet of code will bring a JVM down by filling up the perm gen heap.
for (int i = 0; i < 10000; i++) { new ConfigSlurper().parse("foo = 'bar'"); println i }
8078 8079 8080 Caught: java.lang.OutOfMemoryError: PermGen space at groovy.util.ConfigSlurper.parse(ConfigSlurper.groovy:123)
A line from jmap -permstat
class_loader classes bytes parent_loader alive? type
0x9527de80 23 96536 0x9527d940 dead groovy/lang/GroovyClassLoader$InnerLoader@0x91620470
For every iteration there will be an instance like the one above.
Our application using Groovy config files extensively. It also reloads these files at a frequent rate. This problem is causing quite a bit of pain at the moment.
Any ideas?
--
View this message in context:
http://www.nabble.com/ConfigSlurper---GroovyClassLoader-memory-leak-tp20115910p20115910.html
Sent from the groovy - user mailing list archive at Nabble.com.
--------------------------------------------------------------------- To unsubscribe from this list, please visit:





