[GROOVY-10918] Memory leak: local variable values are not discarded

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0.9
• Fix Version/s: 2.5.22, 3.0.16, 4.0.10
• Component/s: bytecode, Compiler
• Labels: MemoryLeak
• Assignee: Eric Milles
• Reporter: Andriy Rysin
• Created: 26/Jan/23 17:38
• Updated: 13/Mar/23 12:14
• Resolved: 16/Feb/23 15:04

Description

When I run the code below with 3 statements with closures inside the method the local var (parameter) values (all 4 of them) are staying in memory.
I don't see the same problem if I run corresponding Java code with lambdas.

Run TestOOM.groovy with
-Xmx600M -XX:+HeapDumpOnOutOfMemoryError

Notice groovy fails:
Y
Z
java.lang.OutOfMemoryError: Java heap space
Dumping heap to java_pid147612.hprof ...
Heap dump file created [497819587 bytes in 0.136 secs]
Caught: java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
    at test.TestOOM.test(TestOOM.groovy:31)
    at test.TestOOM.run(TestOOM.groovy:41)

But Java version does not.

It looks like all the values of s are still in memory (see screenshot), even though previous values should be discarded.