groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cédric Champeau <cedric.champ...@gmail.com>
Subject Re: Rolling back change to use ClassValue
Date Tue, 08 Sep 2015 18:06:49 GMT
>
>
> Is the memory leak it created worse than the memory leak it fixed?
>
> Yes, because it spreads beyond the boundaries of the classloader Groovy
was loaded in.

> -Pascal
>
>
> Am 08.09.2015 um 09:07 schrieb Cédric Champeau:
>
>> 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