Russell Morrisey created GROOVY-8106:
----------------------------------------

             Summary: Memory leak with expando metaclass in groovy
                 Key: GROOVY-8106
                 URL: https://issues.apache.org/jira/browse/GROOVY-8106
             Project: Groovy
          Issue Type: Bug
    Affects Versions: 2.4.9, 2.4.4
         Environment: Grails 2.5.1 (with updated Groovy version)
Win 7
Java HotSpot 64 v1.8.0_66-b17
            Reporter: Russell Morrisey
         Attachments: BuildConfig.groovy, groovy mem leak.png

I am seeing a memory leak in my Grails app, which uses a lot of expando 
metaclass properties.

>From looking at the GC path, I believe this leak comes from the Groovy 
>framework. I have attached a screenshot from jvisualvm which shows a path to 
>the GC root. The path doesn't appear to contain any weak/soft reference types.

Please let me know if you think my analysis is mistaken. I don't have a strong 
understanding of Groovy framework internals.

GC via JMX does not remove these objects.

Updating my BuildConfig to use Groovy 2.4.9 (with forked compile) did not fix 
the issue.

(Note: Some of the dependencies in the attached BuildConfig are proprietary and 
not available from the grails plugin repo.)




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to