groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paolo Di Tommaso <paolo.ditomm...@gmail.com>
Subject Re: Rolling back change to use ClassValue
Date Tue, 08 Sep 2015 07:18:41 GMT
I think also the issue below will benefit from rolling back to the previous
mechanism.

https://issues.apache.org/jira/browse/GROOVY-7457

And the following conversation
http://www.groovy-lang.org/mailing-lists.html#nabble-td5723731


Cheers,
Paolo


On Tue, Sep 8, 2015 at 10:07 AM, C├ędric Champeau <cedric.champeau@gmail.com>
wrote:

> Hi guys,
>
> As some of you may know, I've been investigating a memory leak which
> involves all versions of Groovy starting from 2.4. The leak comes from a
> bug in the VM regarding how it handles ClassValue, that Groovy 2.4 started
> using. All VMs are affected (7, 8 and 9) and it's still unclear when this
> will be fixed. So I would like to suggest to rollback this change for the
> next release.
>
> Basically, this commit:
> https://github.com/apache/incubator-groovy/commit/97d78e9e52deb52c8e66db501ef208f30384d014
>
> It greatly affects Gradle, so I would suggest to make the change ASAP
> (2.4.5) if everyone agrees.
>

Mime
View raw message