- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Browsing long methods

by Guillermo Polito

Nice, the paragraph is calculated about 7~8 times in a pluggable text morph (depending on the user). And since the composition of a paragraph for a long method takes long (some minutes), it takes 7 times to render it (I've never was able to wait for it. I always lose my patience before). Guille On Mon, May 21, 2012 at 11:41 AM, Guillermo Polito < guillermopolito(a)gmail.com> wrote: > Browsing a long method (lets say, of ~270KB of sourcecode) just hangs the > image. > > Interrupting doesn't even give me control over my image again. It does no > open a debugger, but info is printed in stdout, so I assume that my > UIProcess died, but the event fetcher is still alive... > > One of the processes that get interrupted prints: > > SmallIdentityDictionary(SmallDictionary)>>at:ifAbsent: > MorphExtension>>valueOfProperty:ifAbsent: > MorphExtension>>valueOfProperty: > ScrollBar(Morph)>>valueOfProperty: > ScrollBar(Morph)>>theme > ScrollBar>>normalThumbFillStyle > ScrollBar>>adoptGradientColor: > ScrollBar>>sliderColor: > ScrollBar>>adoptPaneColor: > PluggableMultiColumnListMorph(Morph)>>adoptPaneColor: in Block: [:m | m > adoptPaneColor: paneColor] > > So I just changed #adoptPaneColor: in ScrollBar to do nothing, and I am > able to interrupt again. So it makes me think here it is where the > UIProcess gets killed... > > Now, for the browser stuff, it seems that TextComposer>>#composeAllLines > never finishes. I'm still investigating, but any clue is helpful :). > > Guille >

May 21, 2012

Re: [Pharo-project] SystemNavigationTest>>setUp looks quite strange to me

by Guillermo Polito

On Mon, May 21, 2012 at 7:57 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Hi guillermo > > I saw that you modified > > setUp > super setUp. > > oldMonticelloAnnouncer := SystemAnnouncer privateAnnouncer. > SystemAnnouncer instVarNamed: 'privateAnnouncer' put: nil. > > navigator := self createSystemNavigationToTest. > classFactory := self createClassFactory. > > > Now I would like to understand why? Especially because privateAnnouncer > should not be used and touched. > The problem is that somehow the test is not silent. Executing that test without that makes announcements to be raised with fake classes created on test time, and people subscribed to those announcements break. For example, Nautilus+Rpackage are not expecting classes that are not packaged with RPackage. > SystemAnnouncer privateAnnouncer returns an announcer that should only be > used by internal (not tools). > Actually, it's just a patch to make the tests run. But the real problem is the non-silentlyness of the tests. > > BTW the teardown looks wrong to me. > Yeap, I got it wrong there. But now I do not know if to fix the patch or attack the real issue is the way to go :). Look at my comment in the issue tracker. Guille

May 21, 2012

[Pharo-project] Browsing long methods

by Guillermo Polito

Browsing a long method (lets say, of ~270KB of sourcecode) just hangs the image. Interrupting doesn't even give me control over my image again. It does no open a debugger, but info is printed in stdout, so I assume that my UIProcess died, but the event fetcher is still alive... One of the processes that get interrupted prints: SmallIdentityDictionary(SmallDictionary)>>at:ifAbsent: MorphExtension>>valueOfProperty:ifAbsent: MorphExtension>>valueOfProperty: ScrollBar(Morph)>>valueOfProperty: ScrollBar(Morph)>>theme ScrollBar>>normalThumbFillStyle ScrollBar>>adoptGradientColor: ScrollBar>>sliderColor: ScrollBar>>adoptPaneColor: PluggableMultiColumnListMorph(Morph)>>adoptPaneColor: in Block: [:m | m adoptPaneColor: paneColor] So I just changed #adoptPaneColor: in ScrollBar to do nothing, and I am able to interrupt again. So it makes me think here it is where the UIProcess gets killed... Now, for the browser stuff, it seems that TextComposer>>#composeAllLines never finishes. I'm still investigating, but any clue is helpful :). Guille

May 21, 2012

Re: [Pharo-project] [Sugar-devel] Dr.Geo on XO 1

by StÃ©phane Ducasse

Hilaire how can we reproduce your problem? Stef On May 20, 2012, at 9:41 PM, Hilaire Fernandes wrote: > Is the memory object corrupted in Pharo 1.4? And explain the problem I > have in some situation with DrGeo on XO-1 256MB without swap. > > http://lists.squeak.org/pipermail/vm-dev/2012-May/010652.html > > Hilaire > > > Le 20/05/2012 13:57, Hilaire Fernandes a Ã©crit : >> With Pharo 1.4 (but not with Pharo 1.3) we have a problem leading to the >> crash of DrGeo (based on Pharo 1.4) on low memory machine. >> >> It is clearly a problem related to Pharo 1.4 >> >> Any idea why ? >> >> Hilaire >> >> >> -------- Original Message -------- >> Subject: Re: [Sugar-devel] Dr.Geo on XO 1 >> Date: Sun, 20 May 2012 13:46:01 +0200 >> From: Bert Freudenberg <bert(a)freudenbergs.de> >> To: Sascha Silbe <silbe(a)activitycentral.com> >> CC: Ariel Calzada <ariel.calzada(a)gmail.com>, Hilaire Fernandes >> <hilaire.fernandes(a)edu.ge.ch>, Sugar Devel >> <sugar-devel(a)lists.sugarlabs.org>, Rafael Ortiz >> <rafael(a)activitycentral.com> >> >> >> >> On 20.05.2012, at 11:00, Sascha Silbe wrote: >> >>> Bert Freudenberg <bert(a)freudenbergs.de> writes: >>> >>>> Nope, that was not it. I compiled with -mtune=geode, makes no >>>> difference. >>> >>> Make sure to set -march=<architecture> to something appropriate. -march >>> tells gcc what instructions it can use (so anything that doesn't support >>> these instructions will fail to run the resulting executable), whereas >>> -mtune only tells it to optimise for a certain processor type (but the >>> executable will continue to run on other processors as long as they >>> support the instruction set specified by -march). >> >> I actually had used "-march=pentiumpro -mtune=geode" as recommended here: >> >> http://wiki.laptop.org/go/Geode_LX >> >> and even with an additional -O0 it still crashes. >> >>> In gdb I see it's segfaulting inside the GC logic. It's really >>>> puzzling this only happens on the XO-1 ... >>> >>> You could try booting an XO-1.5 with mem=256M (append that to boot-file >>> in /bootpart/boot/olpc.fth) to simulate the memory pressure of an XO-1. >> >> >> YES! That reproduces the crash on XO-1.5. Good thinking! :) >> >> I could also reproduce it in a virtual Ubuntu 12 with 768 MB RAM (!) but no swap. Top reports: >> >> Mem: 766204k total, 601588k used, 164616k free, 45624k buffers >> Swap: 0k total, 0k used, 0k free, 277024k cached >> >> but DrGeo still crashes. >> >> OTOH, Etoys runs fine using the same Squeak VM on the same system (and on XO-1). So I wonder what the new DrGeo does differently ... >> >> - Bert - >> >> >> >> >> > >

May 21, 2012

[Pharo-project] We need your Pharo successes

by StÃ©phane Ducasse

Again some cool projects done in Pharo :) https://gforge.inria.fr/frs/download.php/30808/pharo-conference-beta9-t3-ea… https://gforge.inria.fr/frs/download.php/30806/pharo-conference-beta9-t3-ho… https://gforge.inria.fr/frs/download.php/30807/pharo-conference-beta9-t3-pr… https://gforge.inria.fr/frs/download.php/30809/ArduinoSoftwareWebPostAutoma… https://gforge.inria.fr/frs/download.php/30810/Loop%20slides.pdf Yes we want more :) Note that this is not only for the conference but we will build a carrousel. Stef

May 21, 2012

Re: [Pharo-project] [Pharo-consortium] We need your Pharo successes

by StÃ©phane Ducasse

Thanks German could you have more bullet lists for the two last slides ? Stef > Mi humble pdf attached. > http://forum.world.st/file/n4631058/ArduinoSoftwareWebPostAutomation.pdf > ArduinoSoftwareWebPostAutomation.pdf > > -- > View this message in context: http://forum.world.st/We-need-your-Pharo-successes-tp4628432p4631058.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

May 21, 2012

[Pharo-project] [update 2.0] #20085

by Esteban Lorenzano

20085 ----- Issue 5929: Some Unix shortcuts needs to be fixed http://code.google.com/p/pharo/issues/detail?id=5929

May 21, 2012

[Pharo-project] SystemNavigationTest>>setUp looks quite strange to me

by StÃ©phane Ducasse

Hi guillermo I saw that you modified setUp super setUp. oldMonticelloAnnouncer := SystemAnnouncer privateAnnouncer. SystemAnnouncer instVarNamed: 'privateAnnouncer' put: nil. navigator := self createSystemNavigationToTest. classFactory := self createClassFactory. Now I would like to understand why? Especially because privateAnnouncer should not be used and touched. SystemAnnouncer privateAnnouncer returns an announcer that should only be used by internal (not tools). BTW the teardown looks wrong to me. Stef

May 21, 2012

Re: [Pharo-project] SciSmalltalk on twitter !

by Serge Stinckwich

On Mon, May 21, 2012 at 10:53 AM, Yanni Chiu <yanni(a)rogers.com> wrote: > On 20/05/12 4:54 PM, Edgar J. De Cleene wrote: >> >> >> On 5/20/12 1:01 PM, "Serge Stinckwich"<serge.stinckwich(a)gmail.com> Â wrote: >> >>> I invite all the students that are working on Smalltalk #gsoc to >>> publish progress of their work on twitter also. >> >> >> +1 > > > -1 > > What's wrong with weekly (or milestone) updates posted someplace. I'm > interested in following along, but not hour by hour. > > Also, whenever I've tried to find old tweets, I would get something like: > search results for old tweets not available - which meant I had to follow > continuously. > > And another thing, trying to track stuff on twitter is like trying to get a > drink from a fire hose. Despite culling and ignoring, it got so out of hand, > I just switched it off. Maybe I'm doing something wrong. Tweets are for sharing progress with people that don't want to follow the project. If you want to follow the project more closely, you can have a look to the Wiki and issues here: https://github.com/SergeStinckwich/SciSmalltalk Regards, -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/

May 21, 2012

Re: [Pharo-project] Morpheas , bringing Morphic to Opengl (3d GUIs)

by chadwick

more detail: after I do GLTTRenderingDemo new openInWorld, I tried dragging a window around in a circle so as to get a feel for what the CPU is doing. The image pauses for increasingly longer times, making the UI unresponsive during this time, eventually locking up entirely.

May 21, 2012