September 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] about the memory leak in Pharo2/Pharo3

by phil＠highoctane.be

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 <estebanlm(a)gmail.com>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 <thierry.goubier(a)cea.fr> > 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 > > > > >

Sept. 19, 2013

Re: [Pharo-dev] Better text needed for contributions

by Stephan Eggermont

Camille wrote: >You need to click on 'resolve' instead of 'edit' I think. Ah, thank you. That works. Stephan

Sept. 19, 2013

Re: [Pharo-dev] Better text needed for contributions

by Camille Teruel

On 19 sept. 2013, at 17:06, Stephan Eggermont wrote: >> Track and tag your change/Fix/Enhancement: >> â¢ Add an entry to the Issues tracker describing your change (include the package version name of the package). Set the status to "Fixed". > > That doesn't work. Possible status changes are 'Working on' and 5 variations on 'Work needed'. > And 11628 is fixed > You need to click on 'resolve' instead of 'edit' I think. > Stephan > >

Sept. 19, 2013

Fwd: PhaROS - VirtualBox.

by Santiago Bragagnolo

Hi all! For people that went ESUG probaby this is already known, but, in Ecole des mines de Douai we are working in PhaROS, which is a client framework for ROS operative system. So, if you are interested in get a bit into or deeper, here is a link. http://car.mines-douai.fr/2013/09/pharos-virtualbox-image/ There you can find an explaining post and a link to a virtualbox image with everything installed :). We will have an issue tracker soon, meanwhile, if you use it and you have blames or issues, send me email with [PhaROS] in the subject please! Thank you very much, i hope you enjoy it :). Santiago.

Sept. 19, 2013

Re: [Pharo-dev] Stability of 3.0

by StÃ©phane Ducasse

Ok probably linked to the changes made by fernando while removing translucentColor. Stef On Sep 19, 2013, at 5:36 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > TranslucentPatterns is undefined. > > Error: Instances of UndefinedObject are not indexable > in FormCanvas>>translucentMaskFor:depth: > > Thierry > > > Le 19/09/2013 17:24, StÃ©phane Ducasse a Ã©crit : >> >> On Sep 19, 2013, at 5:24 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >> >>> Hi all, >>> >>> is it me or what? The latest 3.0 gives me a lot of red squares a bit everywhere around the place, making working with it a bit (a lot!) painful. >> >> I do not know because busy with lecture writing and managing mess. >> >> Can you grab the debug button (I know this is unclear) >> but if you get the faulty morph you can get a debugger and we can see what is the message that is failing. >> It saved lot of work and frsutration because you know why you get the red cross of death. >> Stef >> >>> >>> I'm on 30407, frech from get.pharo.org. >>> >>> Thierry >>> -- >>> 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 >>> >> >> >> >> > > -- > 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 >

Sept. 19, 2013

Re: [Pharo-dev] about the memory leak in Pharo2/Pharo3

by Goubier Thierry

Ok. I've looked at the first slice (step 1/2 of 3 :)) and it seems doable. But I don't think I'll be able to do step 2 and 3 :( Thierry Le 19/09/2013 17:26, StÃ©phane Ducasse a Ã©crit : >>From what I understand: > > - on: do: register the block context as the receiver to kick in the block evaluation > => weak registration is then not weak anymore > > - there was an old LegacyRegistrationMechanism that works (fallback for old VM that do not > have the right way of managing weak structure) and the LegacyRegistration got some > on:do: and grew grew grew. > > Stef > > > > On Sep 19, 2013, at 5:30 PM, Goubier Thierry <thierry.goubier(a)cea.fr> 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 >> > > > > -- 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

Sept. 19, 2013

Re: [Pharo-dev] Stability of 3.0

by Goubier Thierry

TranslucentPatterns is undefined. Error: Instances of UndefinedObject are not indexable in FormCanvas>>translucentMaskFor:depth: Thierry Le 19/09/2013 17:24, StÃ©phane Ducasse a Ã©crit : > > On Sep 19, 2013, at 5:24 PM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > >> Hi all, >> >> is it me or what? The latest 3.0 gives me a lot of red squares a bit everywhere around the place, making working with it a bit (a lot!) painful. > > I do not know because busy with lecture writing and managing mess. > > Can you grab the debug button (I know this is unclear) > but if you get the faulty morph you can get a debugger and we can see what is the message that is failing. > It saved lot of work and frsutration because you know why you get the red cross of death. > Stef > >> >> I'm on 30407, frech from get.pharo.org. >> >> Thierry >> -- >> 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 >> > > > > -- 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

Sept. 19, 2013

Re: [Pharo-dev] about the memory leak in Pharo2/Pharo3

by Esteban Lorenzano

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 <thierry.goubier(a)cea.fr> 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 >

Sept. 19, 2013

Re: [Pharo-dev] about the memory leak in Pharo2/Pharo3

by Goubier Thierry

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

Sept. 19, 2013

Re: [Pharo-dev] [update 3.0] #30410

by Goubier Thierry

How did you solve that? Thierry Le 19/09/2013 17:16, Esteban Lorenzano a Ã©crit : > 30410 > ----- > > 11544 Memory leak when using weak announcements with blocks > https://pharo.fogbugz.com/f/cases/11544 > > (step 3/3) > > Diff information: > http://smalltalkhub.com/mc/Pharo/Pharo30/main/RPackage-Tests-EstebanLorenza… > http://smalltalkhub.com/mc/Pharo/Pharo30/main/RPackage-SystemIntegration-Es… > > > > -- 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

Sept. 19, 2013