February 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] Traits in PHP

by blake

This is kinda cool: http://phpmaster.com/using-traits-in-php-5-4/

Feb. 15, 2012

Re: [Pharo-project] garbage collection

by Igor Stasenko

.. and perhaps we should tell Chris to check Magma code about potential leak by preventing unregistering external semaphores. of course, that could be Pharo bug as well. On 15 February 2012 02:11, Igor Stasenko <siguctua(a)gmail.com> wrote: > So, what i suggest you to do is to replace Array with WeakArray in > > ExternalSemaphoreTable>>clearExternalObjects > > and restart the image, so change will be put in effect. > > And report an observation if it cures the problem (and not adds new ones ;). > > On 15 February 2012 01:23, Milan Mimica <milan.mimica(a)gmail.com> wrote: >> | semaphores arr res | >> >> arr := ExternalSemaphoreTable unprotectedExternalObjects. >> semaphores := arr reject: #isNil. >> >> res := semaphores collect: [:sema | sema pointersTo reject: [:ptr | ptr == >> arr or: [ptr == semaphores ] ] ]. >> res := res select: [ :each | each isEmpty ]. >> res size. >> >> Yes, that's what I did, I'm sure. All of my images, except a fresh 1.4, >> answer a number >0. >> >> >> On 15 February 2012 00:11, Igor Stasenko <siguctua(a)gmail.com> wrote: >>> >>> On 15 February 2012 00:54, Milan Mimica <milan.mimica(a)gmail.com> wrote: >>> > On 14 February 2012 22:55, Igor Stasenko <siguctua(a)gmail.com> wrote: >>> >> >>> >> >>> >> semaphores collect: [:sema | >>> >> Â Â Â Â sema -> >>> >> Â Â Â Â Â Â Â Â (sema pointersTo reject: [:ptr | ptr == arr or: [ptr == >>> >> semaphores ] ] ) ] >>> >> >>> >> Can you try invoking it on your image , look for those who has an >>> >> empty array, which will mean that there is no references to it except >>> >> semaphore table itself. >>> > >>> > >>> > There is 69 of such semaphores, out ofÂ hundredsÂ in total. Not much :-/ >>> > On a normal image there is only a few. >>> > >>> >>> So, we got a leak somewhere. Can you double-check, >>> this is semaphores which in the list which >>> when you inspect that list >>> will show entries like >>> >>> a Semaphore() -> #() >>> >>> but not a total number of entries. >>> >>> Oh, ok lets just change the code: >>> >>> | semaphores arr | >>> >>> arr := ExternalSemaphoreTable unprotectedExternalObjects. >>> semaphores := arr reject: #isNil. >>> >>> semaphores reject: [:sema | >>> Â Â Â (sema pointersTo reject: [:ptr | ptr == arr or: [ptr == >>> semaphores ] ] ) isEmpty not ] >>> >>> so, normally this code should answer an empty array. >>> If not, then there's leak >>> >>> -- >>> Best regards, >>> Igor Stasenko. >>> >> >> >> >> -- >> Milan Mimica >> http://sparklet.sf.net > > > > -- > Best regards, > Igor Stasenko. -- Best regards, Igor Stasenko.

Feb. 15, 2012

Re: [Pharo-project] garbage collection

by Igor Stasenko

So, what i suggest you to do is to replace Array with WeakArray in ExternalSemaphoreTable>>clearExternalObjects and restart the image, so change will be put in effect. And report an observation if it cures the problem (and not adds new ones ;). On 15 February 2012 01:23, Milan Mimica <milan.mimica(a)gmail.com> wrote: > | semaphores arr res | > > arr := ExternalSemaphoreTable unprotectedExternalObjects. > semaphores := arr reject: #isNil. > > res := semaphores collect: [:sema | sema pointersTo reject: [:ptr | ptr == > arr or: [ptr == semaphores ] ] ]. > res := res select: [ :each | each isEmpty ]. > res size. > > Yes, that's what I did, I'm sure. All of my images, except a fresh 1.4, > answer a number >0. > > > On 15 February 2012 00:11, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> On 15 February 2012 00:54, Milan Mimica <milan.mimica(a)gmail.com> wrote: >> > On 14 February 2012 22:55, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> >> >> >> >> semaphores collect: [:sema | >> >> Â Â Â Â sema -> >> >> Â Â Â Â Â Â Â Â (sema pointersTo reject: [:ptr | ptr == arr or: [ptr == >> >> semaphores ] ] ) ] >> >> >> >> Can you try invoking it on your image , look for those who has an >> >> empty array, which will mean that there is no references to it except >> >> semaphore table itself. >> > >> > >> > There is 69 of such semaphores, out ofÂ hundredsÂ in total. Not much :-/ >> > On a normal image there is only a few. >> > >> >> So, we got a leak somewhere. Can you double-check, >> this is semaphores which in the list which >> when you inspect that list >> will show entries like >> >> a Semaphore() -> #() >> >> but not a total number of entries. >> >> Oh, ok lets just change the code: >> >> | semaphores arr | >> >> arr := ExternalSemaphoreTable unprotectedExternalObjects. >> semaphores := arr reject: #isNil. >> >> semaphores reject: [:sema | >> Â Â Â (sema pointersTo reject: [:ptr | ptr == arr or: [ptr == >> semaphores ] ] ) isEmpty not ] >> >> so, normally this code should answer an empty array. >> If not, then there's leak >> >> -- >> Best regards, >> Igor Stasenko. >> > > > > -- > Milan Mimica > http://sparklet.sf.net -- Best regards, Igor Stasenko.

Feb. 15, 2012

Re: [Pharo-project] garbage collection

by Milan Mimica

| semaphores arr res | arr := ExternalSemaphoreTable unprotectedExternalObjects. semaphores := arr reject: #isNil. res := semaphores collect: [:sema | sema pointersTo reject: [:ptr | ptr == arr or: [ptr == semaphores ] ] ]. res := res select: [ :each | each isEmpty ]. res size. Yes, that's what I did, I'm sure. All of my images, except a fresh 1.4, answer a number >0. On 15 February 2012 00:11, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 15 February 2012 00:54, Milan Mimica <milan.mimica(a)gmail.com> wrote: > > On 14 February 2012 22:55, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> > >> > >> semaphores collect: [:sema | > >> sema -> > >> (sema pointersTo reject: [:ptr | ptr == arr or: [ptr == > >> semaphores ] ] ) ] > >> > >> Can you try invoking it on your image , look for those who has an > >> empty array, which will mean that there is no references to it except > >> semaphore table itself. > > > > > > There is 69 of such semaphores, out of hundreds in total. Not much :-/ > > On a normal image there is only a few. > > > > So, we got a leak somewhere. Can you double-check, > this is semaphores which in the list which > when you inspect that list > will show entries like > > a Semaphore() -> #() > > but not a total number of entries. > > Oh, ok lets just change the code: > > | semaphores arr | > > arr := ExternalSemaphoreTable unprotectedExternalObjects. > semaphores := arr reject: #isNil. > > semaphores reject: [:sema | > (sema pointersTo reject: [:ptr | ptr == arr or: [ptr == > semaphores ] ] ) isEmpty not ] > > so, normally this code should answer an empty array. > If not, then there's leak > > -- > Best regards, > Igor Stasenko. > > -- Milan Mimica http://sparklet.sf.net

Feb. 14, 2012

Re: [Pharo-project] garbage collection

by Igor Stasenko

On 15 February 2012 01:18, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 15 February 2012 01:11, Igor Stasenko <siguctua(a)gmail.com> wrote: >> On 15 February 2012 00:54, Milan Mimica <milan.mimica(a)gmail.com> wrote: >>> On 14 February 2012 22:55, Igor Stasenko <siguctua(a)gmail.com> wrote: >>>> >>>> >>>> semaphores collect: [:sema | >>>> Â Â Â Â sema -> >>>> Â Â Â Â Â Â Â Â (sema pointersTo reject: [:ptr | ptr == arr or: [ptr == >>>> semaphores ] ] ) ] >>>> >>>> Can you try invoking it on your image , look for those who has an >>>> empty array, which will mean that there is no references to it except >>>> semaphore table itself. >>> >>> >>> There is 69 of such semaphores, out ofÂ hundredsÂ in total. Not much :-/ >>> On a normal image there is only a few. >>> >> >> So, we got a leak somewhere. Can you double-check, >> this is semaphores which in the list which >> when you inspect that list >> will show entries like >> >> a Semaphore() -> #() >> >> but not a total number of entries. >> >> Oh, ok lets just change the code: >> >> | semaphores arr | >> >> arr := ExternalSemaphoreTable unprotectedExternalObjects. >> semaphores := arr reject: #isNil. >> >> semaphores reject: [:sema | >> Â Â Â (sema pointersTo reject: [:ptr | ptr == arr or: [ptr == >> semaphores ] ] ) isEmpty not ] >> >> so, normally this code should answer an empty array. >> If not, then there's leak >> > > btw, i found it strange that #pointersTo does not reports a context of > closure, which apparently > holds a strong reference to semaphore, i.e. the following must yield true: > > > | sema | > sema := Semaphore new. > sema pointersTo includes: thisContext > ah, ok, it seems to be intended by implementation: objectsToAlwaysExclude := { thisContext. thisContext sender. thisContext sender sender. objectsToExclude. }. > > > -- > Best regards, > Igor Stasenko. -- Best regards, Igor Stasenko.

Feb. 14, 2012

Re: [Pharo-project] garbage collection

by Igor Stasenko

On 15 February 2012 01:11, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 15 February 2012 00:54, Milan Mimica <milan.mimica(a)gmail.com> wrote: >> On 14 February 2012 22:55, Igor Stasenko <siguctua(a)gmail.com> wrote: >>> >>> >>> semaphores collect: [:sema | >>> Â Â Â Â sema -> >>> Â Â Â Â Â Â Â Â (sema pointersTo reject: [:ptr | ptr == arr or: [ptr == >>> semaphores ] ] ) ] >>> >>> Can you try invoking it on your image , look for those who has an >>> empty array, which will mean that there is no references to it except >>> semaphore table itself. >> >> >> There is 69 of such semaphores, out ofÂ hundredsÂ in total. Not much :-/ >> On a normal image there is only a few. >> > > So, we got a leak somewhere. Can you double-check, > this is semaphores which in the list which > when you inspect that list > will show entries like > > a Semaphore() -> #() > > but not a total number of entries. > > Oh, ok lets just change the code: > > | semaphores arr | > > arr := ExternalSemaphoreTable unprotectedExternalObjects. > semaphores := arr reject: #isNil. > > semaphores reject: [:sema | > Â Â Â (sema pointersTo reject: [:ptr | ptr == arr or: [ptr == > semaphores ] ] ) isEmpty not ] > > so, normally this code should answer an empty array. > If not, then there's leak > btw, i found it strange that #pointersTo does not reports a context of closure, which apparently holds a strong reference to semaphore, i.e. the following must yield true: | sema | sema := Semaphore new. sema pointersTo includes: thisContext -- Best regards, Igor Stasenko.

Feb. 14, 2012

Re: [Pharo-project] garbage collection

by Igor Stasenko

On 15 February 2012 00:54, Milan Mimica <milan.mimica(a)gmail.com> wrote: > On 14 February 2012 22:55, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> >> semaphores collect: [:sema | >> Â Â Â Â sema -> >> Â Â Â Â Â Â Â Â (sema pointersTo reject: [:ptr | ptr == arr or: [ptr == >> semaphores ] ] ) ] >> >> Can you try invoking it on your image , look for those who has an >> empty array, which will mean that there is no references to it except >> semaphore table itself. > > > There is 69 of such semaphores, out ofÂ hundredsÂ in total. Not much :-/ > On a normal image there is only a few. > So, we got a leak somewhere. Can you double-check, this is semaphores which in the list which when you inspect that list will show entries like a Semaphore() -> #() but not a total number of entries. Oh, ok lets just change the code: | semaphores arr | arr := ExternalSemaphoreTable unprotectedExternalObjects. semaphores := arr reject: #isNil. semaphores reject: [:sema | (sema pointersTo reject: [:ptr | ptr == arr or: [ptr == semaphores ] ] ) isEmpty not ] so, normally this code should answer an empty array. If not, then there's leak -- Best regards, Igor Stasenko.

Feb. 14, 2012

Re: [Pharo-project] garbage collection

by Milan Mimica

On 14 February 2012 22:55, Igor Stasenko <siguctua(a)gmail.com> wrote: > > semaphores collect: [:sema | > sema -> > (sema pointersTo reject: [:ptr | ptr == arr or: [ptr == > semaphores ] ] ) ] > > Can you try invoking it on your image , look for those who has an > empty array, which will mean that there is no references to it except > semaphore table itself. > There is 69 of such semaphores, out of hundreds in total. Not much :-/ On a normal image there is only a few. -- Milan Mimica http://sparklet.sf.net

Feb. 14, 2012

[Pharo-project] annoying press "ok" when running tests (not headless)

by Igor Stasenko

i started tests and leaved image for a while, but when i went back hoping that it already finished, i discovered that it waiting for me to press ok and did not ran even 20% of all tests. Somewhere in GoferOperationTest>>testMerge it says 'No changes' and waits for the user to press 'ok' -- Best regards, Igor Stasenko.

Feb. 14, 2012

Re: [Pharo-project] Feedback from lecture :(

by Igor Stasenko

On 15 February 2012 00:03, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > On Tue, Feb 14, 2012 at 11:52 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> On 14 February 2012 20:22, Lukas Renggli <renggli(a)gmail.com> wrote: >> >>> students in the lecture on windows downloaded cogvm I do not from >> >>> whereâ¦ >> >>> and used pharo1.3 and >> >>> some experienced crashes. >> >> >> >> This has been reported at least 10 times per week since the last 6 >> >> months. >> >> The VMs of the one click are FUC.. old and buggy. If nobody have time >> >> to >> >> make a new one click (we are all busy), please please please, remove it >> >> from >> >> the website. We give so much bad impression. It is worst than having no >> >> one >> >> click. >> > >> > You cannot say that, because I updated the One-Click distribution less >> > than a month ago: >> > >> > >> > https://github.com/renggli/builder/commit/7623726096db2e3fa58eefe267c62ba17… >> > >> > People using this code get the latest available CogVM. The problem is >> > that Pharo maintains its own unmaintained fork. >> > >> >> Huh? >> >> See the build history: >> https://ci.lille.inria.fr/pharo/view/Cog/job/Cog-Unix/ >> >> last build 26 Jan >> >> https://ci.lille.inria.fr/pharo/view/Cog/job/StackVM-Mac-Cocoa-blessed/ >> again, last build 28 Jan. >> >> Here just a list of changes in latest builds: >> (you can find them here: >> >> https://ci.lille.inria.fr/pharo/view/Cog/job/Cog%20Git%20Tracker%20%28bless… >> ) >> Changes >> #26 (Jan 26, 2012 5:33:21 PM) >> >> Â Â replaced spaces with tabs â camillobruni / detail >> >> #25 (Jan 26, 2012 5:18:48 PM) >> >> Â Â added new pharo scropt â camillobruni / detail >> Â Â - fixed configuraiton to open a Workspace with example >> configurations â camillobruni / detail >> Â Â trying to fix issues with the command line arguments â camillobruni / >> detail >> Â Â more work on the image script and the howto â camillobruni / detail >> Â Â tried to implemention dir_lookupEntry for Cococa OSX â camillobruni / >> detail >> Â Â extended howto with osx gcc change â camillobruni / detail >> Â Â fixed back opengl changes â camillobruni / detail >> Â Â fixed VM path, returning bundlepath with app name â camillobruni / >> detail >> Â Â implemented direEntryLookup and refactored a bit the source code â >> camillobruni / detail >> Â Â more howto â camillobruni / detail >> Â Â minor change in the HOWTO â camillobruni / detail >> Â Â undoing accidental changes â camillobruni / detail >> >> #23 (Jan 25, 2012 8:06:27 PM) >> >> Â Â removed deprecated calls to recordKeystroke â guillermopolito / detail >> Â Â removed unused comment â guillermopolito / detail >> Â Â removed old code â guillermopolito / detail >> Â Â removed dead code â guillermopolito / detail >> Â Â removed dead code â guillermopolito / detail >> Â Â removed lot of debug only code â guillermopolito / detail >> Â Â removed temporal file â guillermopolito / detail >> Â Â removed more debug printfs â guillermopolito / detail >> Â Â formatted the code â guillermopolito / detail >> Â Â little style change â guillermopolito / detail >> Â Â added mappings to numeric keypad â guillermopolito / detail >> Â Â added comments to unicode conversion â guillermopolito / detail >> Â Â more comments â guillermopolito / detail >> >> For the full list of changes in VM , visit >> https://gitorious.org/cogvm/blessed/commits/master >> >> but just don't say bullshit like unmaintained unmaintained VM. > > > The substantive change is the ephemeron changes. Â I'm not convinced that > this code is correct. Â I'm convinced that the approach is wrong. Â See my > postings on using the format word to encode ephemeronness. > I remember that, Eliot. And i agreed with you that it is not optimal. You also told back then, that you will introduce it soon, so i suspended any activities in that regard. I can revert that code from VM in no time, if you think it is the one, which makes VM unstable. Which i doubt, since ephemerons is not in use by image, so the code in question simply does an empty run, resulting same semantics as in your branch. But i will check it once more. -- Best regards, Igor Stasenko.

Feb. 14, 2012