-
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
-
Component/s: None
-
Labels:None
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
- is related to
-
GROOVY-8189 OutOfMemoryError with groovy.use.classvalue=false
-
- Open
-
-
GROOVY-7623 IBM Java (J9) ClassValue works correctly so should use it by default
-
- Closed
-
-
GROOVY-8199 Re-enable use of ClassValue for all JDKs
-
- Open
-
- relates to
-
GROOVY-6704 Memory leak in ClassInfo when using MetaClasses
-
- Closed
-
-
GROOVY-7457 NPE exception on ManagedLinkedList
-
- Closed
-