You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2017/05/15 09:24:04 UTC
[jira] [Commented] (GROOVY-7591) Use of ClassValue causes major
memory leak
[ https://issues.apache.org/jira/browse/GROOVY-7591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16010219#comment-16010219 ]
Jochen Kemnade commented on GROOVY-7591:
----------------------------------------
It seems that GROOVY-7683 caused this issue after all. Shouldn't {{ClassValue}} be enabled by default again?
> Use of ClassValue causes major memory leak
> ------------------------------------------
>
> Key: GROOVY-7591
> URL: https://issues.apache.org/jira/browse/GROOVY-7591
> Project: Groovy
> Issue Type: Improvement
> Affects Versions: 2.4.0, 2.4.1, 2.4.2, 2.4.3, 2.4.4
> Reporter: Cédric Champeau
> Assignee: Cédric Champeau
> Fix For: 2.4.5
>
>
> 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}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)