thanks It will help us. We got some internal reorganisation right now because fernando is leaving the team.
stef On Sep 19, 2013, at 10:42 PM, GOUBIER Thierry <[email protected]> wrote: > Ok, I've added issue 11639 for the backport. > > I'll make a try tonight. > > Thierry > ________________________________________ > De : Pharo-dev [[email protected]] de la part de Esteban > Lorenzano [[email protected]] > Date d'envoi : jeudi 19 septembre 2013 17:33 > À : Pharo Development List > Objet : Re: [Pharo-dev] about the memory leak in Pharo2/Pharo3 > > is a really annoying combination of problems: > > 1) the abuse of on:do: for register announcers, usually in SystemAnnouncer > singleton, who then register immortal announcements. > 2) the abuse of weak message in places where is not needed (like in non > global announcements who then will be collected when owner collected) > 3) a weird case when instead a WeakAnnouncementSubscription, system was > registering LegacyWeakSubscription, and this one uses WeakRegistry (which is > a singleton too)... so, if combined with #on:do:, the subscriptions were > becoming immortal too. > > So far, we think that is all the problem. > > You need two steps (the 3rd was because I forgot to commit something :p) > because after changing somethign in the finalization process, you then need > to restart it to be able to remove old/not used methods. > > cheers, > Esteban > > On Sep 19, 2013, at 5:30 PM, Goubier Thierry <[email protected]> wrote: > >> >> >> Le 19/09/2013 17:20, Esteban Lorenzano a écrit : >>> Hi, >>> >>> I just submitted and integrated a fix for the leak problem. >>> That should fix the problem we are having in Pharo3... now we need to work >>> on a backport for Pharo2... any takers? :) >> >> I need some explanations :) >> >> Thierry >> >>> Esteban >>> >>> >> >> -- >> Thierry Goubier >> CEA list >> Laboratoire des Fondations des Systèmes Temps Réel Embarqués >> 91191 Gif sur Yvette Cedex >> France >> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >> > > >
