[
https://issues.apache.org/jira/browse/GROOVY-10232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472490#comment-17472490
]
Chad Wilson commented on GROOVY-10232:
--------------------------------------
Thanks for the work here! I've been scratching my head about which change has
caused instability on builds for [https://github.com/gocd/gocd/] for some time,
but suspect this one.
Does anyone know if this is likely to have affected all 3.0.x versions, or only
a particular point/patch release - i.e could a downgrade to an earlier 3.0.x
version help?
> 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-rc-3
>
> 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)
