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

["Paul King (Jira)" <ji...@apache.org>]

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

Paul King edited comment on GROOVY-10232 at 11/18/21, 9:42 PM:
---------------------------------------------------------------

[~papegaaij] Just FYI, there is a switch for Spock for working with Groovy 4 - it is used by the Groovy build for instance.
[https://github.com/apache/groovy/blob/master/buildSrc/src/main/groovy/org.apache.groovy-base.gradle#L220]


was (Author: paulk):
Just FYI, there is a switch for Spock for working with Groovy 4 - it is used by the Groovy build for instance.
https://github.com/apache/groovy/blob/master/buildSrc/src/main/groovy/org.apache.groovy-base.gradle#L220

> 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
>            Priority: Major
>         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)