Good news... I saw that Seaside 3.x was okay with Pharo 3.
I am starting a new project. Should I start with Pharo3 right away? Phil On Thu, Sep 19, 2013 at 5:33 PM, Esteban Lorenzano <[email protected]>wrote: > 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 > > > > >
