On Sep 4, 2013, at 9:55 AM, Esteban Lorenzano <esteba...@gmail.com> wrote:
>>> 
>>> 
>> We are in the process of fixing them, but have not fixed all yet. I always 
>> thought that we would
>> back port when we have fixed the problem completely in 3.0
> 
> I'm not sure what we are seeing in pharo3 is the same problem reported in 
> pharo2. 
> Of course if it is, we will backport. 
> But "inflation" problem in ph3 is very consistent and repeatable, the problem 
> reported in ph2... well, I never seen it before, and we have just one report 
> (and I assume that we have more than one hundred production projects with 
> that version). 
> So is likely something different (also some of the detected leaks are due to 
> changes in ph3, not present in the older version). 
> 

Yes, the problem in Pharo2 seems to be related purely to morph extensions 
hanging around.

        
https://pharo.fogbugz.com/f/cases/11290/There-are-far-more-instances-of-MorphExtension-than-Morph

(yes, I should have added a parent case for "back port to 2.0").

        Marcus

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to