[GROOVY-7591] Use of ClassValue causes major memory leak

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.4.0, 2.4.1, 2.4.2, 2.4.3, 2.4.4
• Fix Version/s: 2.4.5
• Assignee: Cédric Champeau
• Reporter: Cédric Champeau
• Created: 13/Sep/15 11:45
• Updated: 23/May/17 10:12
• Resolved: 13/Sep/15 11:47

Description

Following the discussion at http://mail-archives.apache.org/mod_mbox/incubator-groovy-dev/201509.mbox/%3CCADQzvm%3DvCHR7c1-uaCMkEq7i58ofvvaUrnqHjiGxMp0YQFuc5w%40mail.gmail.com%3E

And the JDK bug https://bugs.openjdk.java.net/browse/JDK-8136353

We suggest to disable use of ClassValue by default until bug is fixed in the JDK. There's a system property which will let the user reactivate use of ClassValue: groovy.use.classvalue

Issue Links

• is related to: GROOVY-8189 OutOfMemoryError with groovy.use.classvalue=false
• is related to: GROOVY-7623 IBM Java (J9) ClassValue works correctly so should use it by default
• is related to: GROOVY-8199 Re-enable use of ClassValue for all JDKs
• relates to: GROOVY-6704 Memory leak in ClassInfo when using MetaClasses
• relates to: GROOVY-7457 NPE exception on ManagedLinkedList