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

Emond Papegaaij commented on GROOVY-10232:
------------------------------------------

[~paulk] It's not just Spock, but our entire infrastructure to run tests. Our 
tests are based on Arquillian, so for Groovy 4 to work, I will need to update 
our integration for Spock and Arquillian 
(https://github.com/topicusonderwijs/arquillian-testrunner-spock/tree/spock-2.0-junit5)
 as well. Also, because the maven coordinates have changed, this will need to 
be changed in our packaging as well, because Arquillian will need to know which 
classes to include with the tests to run. As you might understand, this will 
require a significant effort and the results will not be entirely reliable, 
because it's all based on experimental releases and things that are not built 
to work together.

The patch applies cleanly on the GROOVY_3.0.X branch, so I did a run with that 
version. It looks like the problem is fixed. I've reduced the memory settings 
to the values we used for Groovy 2.5 and no longer get an OutOfMemoryError.

> 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)

Reply via email to