[jira] [Commented] (GROOVY-10232) Massive increase in memory usage due to CacheableCallSite

["Chad Wilson (Jira)" <ji...@apache.org>]

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

Chad Wilson commented on GROOVY-10232:
--------------------------------------

I see 4.0.0 is GA as of 11 days ago (congratulations!), and there is quite a bit work on 3.0.10 going on based on https://github.com/apache/groovy/commits/GROOVY_3_0_X - hopefully we are close to a release here :)

> Massive increase in memory usage due to CacheableCallSite
> ---------------------------------------------------------
>
>                 Key: GROOVY-10232
>                 URL: https://issues.apache.org/jira/browse/GROOVY-10232
>             Project: Groovy
>          Issue Type: Bug
>          Components: groovy-runtime
>    Affects Versions: 3.0.9
>            Reporter: Emond Papegaaij
>            Assignee: Daniel Sun
>            Priority: Major
>             Fix For: 3.0.10, 4.0.0
>
>         Attachments: Screenshot_20210913_161502.png
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> When upgrading our tests from Spock 1.3 with Groovy 2.5 to Spock 2.0 with Groovy 3.0.9, we are seeing issue with memory usage caused by CacheableCallSite. This memory seems to be retained in classes and is therefore never freed. A single Spock test class can take as much as 150mb memory. The total amount of memory sums up to several gigabytes of additional memory, causing our tests to take about 3 times as much memory as with Spock 1.3 and Groovy 2.5.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)