[
https://issues.apache.org/jira/browse/GROOVY-10232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470744#comment-17470744
]
Ian Springer commented on GROOVY-10232:
---------------------------------------
My team also encountered this issue with our Groovy test suites after upgrading
from Groovy 2.x to Groovy 3.0.9. We are running our tests on GraalVM 21.2.0
(JDK 11.0.12) with TestNG 6.14.3. We increased the max heap size for our
integration test suite from 4 GB to 18 GB and still ran out of heap. At the
point when the JVM ran out of heap there were 108K instances of
CacheableCallSite consuming 18.5 GB (96%) of the heap.
We are going to try the patch from PR 1647, but would prefer not having to fork
Groovy to work around this issue. We noticed PR 1647 has been closed. Does the
Groovy team still plan on addressing this issue?
Thanks!
> 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)
