July 2015 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [Moose-dev] Re: Script of the day

by H. Hirzel

thanks, layout force is very nice. But my question is about a tree map. Like the one here https://en.wikipedia.org/wiki/File:Gradient_grouped_treemap.jpg treemap is not known. --Hannes On 7/30/15, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > You should be able to specify all layouts available in roassal... > > b layout tree. > b layout cluster. > b layout force. > ... > > Peter > > -----Original Message----- > From: "H. Hirzel" <hannes.hirzel(a)gmail.com> > Sent: â7/â30/â2015 8:40 PM > To: "Moose-related development" <moose-dev(a)iam.unibe.ch>; > "pharo-users(a)lists.pharo.org" <pharo-users(a)lists.pharo.org> > Subject: Re: [Pharo-users] [Moose-dev] Re: Script of the day > > Is it possible to use a tree map? > > --Hannes > > On 7/30/15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> I gave a try, and I did not find anything weird. >> I guess your document folder contains many files, as Doru said >> >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >>> On Jul 30, 2015, at 5:51 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> >>> wrote: >>> >>> Frankly I dont mind big images or big data , neither I share the >>> obsession >>> to shrink things down to few mbs in a time that we are talking in TBs . >>> >>> Anyway you asked for the image and this is a link to it >>> >>> https://www.dropbox.com/s/wh1071xgoo54fq7/1%20Ephestos%2027-05-15.zip?dl=0 >>> <https://www.dropbox.com/s/wh1071xgoo54fq7/1%20Ephestos%2027-05-15.zip?dl=0> >>> >>> I dont think you will find anything abnormal about it though. >>> >>> I was wondering whether it would worth the effort beyond the unit tests >>> that check for behaviour of the code to have also benchmark tests that >>> will have to pass specific standards so that specific method must >>> perform >>> under a strict timetable specific tasks, this way CI may alert not only >>> unit tests that fail but also benchmarks that fail , automagically. >>> >>> Maybe some food for thought. >>> >>> Personally I am far more worried how much CPU Pharo consumes than how >>> much >>> RAM. >>> >>> On Wed, Jul 29, 2015 at 11:54 PM Peter UhnÃ¡k <i.uhnak(a)gmail.com >>> <mailto:i.uhnak@gmail.com>> wrote: >>> Not sure if there is any downside (I've been using it for a long time >>> without problems), but image cleanup often does wonders for me. >>> >>> Moose image >>> 410 MB => cleanup (World -> System -> Do Image Cleanup) => save => 237 >>> MB >>> and I even had situations where it went from ~600 MB to ~60 MB. >>> (As to why my images are so massive... right now there are 19 windows >>> opened inside most of them with opened roassal visualization... and I am >>> saving like every five minutes... but that is just a guess.) >>> >>> But image cleanup is supposed to break things, so better to backup the >>> folder first. >>> Plus is cache really necessary? I mean it's a cache. .image + .changes >>> should usually suffice. >>> >>> Peter >>> >>> On Wed, Jul 29, 2015 at 10:45 PM, Dimitris Chloupis >>> <kilon.alios(a)gmail.com >>> <mailto:kilon.alios@gmail.com>> wrote: >>> Tudor I dont know if you received my message but I already answered that >>> with this: >>> >>> "ah ok then its normal. Yes the structure is extensive, its 13 folders >>> (the rest 71 are files some of them very big), I would not be surprised >>> if >>> each contains 100 files in its own subfolders." >>> >>> >>> >>> On Wed, Jul 29, 2015 at 11:30 PM Tudor Girba <tudor(a)tudorgirba.com >>> <mailto:tudor@tudorgirba.com>> wrote: >>> Hi, >>> >>> But, do you confirm that you have many files under the mentioned folder? >>> >>> Cheers, >>> Doru >>> >>> >>> >>> On Wed, Jul 29, 2015 at 10:25 PM, Dimitris Chloupis >>> <kilon.alios(a)gmail.com >>> <mailto:kilon.alios@gmail.com>> wrote: >>> the image is 180 mb, changes are another 15, there are several other >>> folders that raise the total size to 250 mb, monticello-cache and >>> github-cache prodominately. >>> >>> Hmm ok my bad, the size of the zip is 89 MB not 200 mb. Still will take >>> me >>> 1-2 hours to upload on this connection. So if you guys still need the >>> image i can upload tommorow from work, though it seems my slow down is >>> normal. >>> >>> Afterall I am sure you can test it yourselves on complex file structures >>> to see if it has delays as long as 20 minutes. >>> >>> >>> >>> On Wed, Jul 29, 2015 at 11:01 PM Sven Van Caekenberghe <sven(a)stfx.eu >>> <mailto:sven@stfx.eu>> wrote: >>> >>> > On 29 Jul 2015, at 21:33, Dimitris Chloupis <kilon.alios(a)gmail.com >>> > <mailto:kilon.alios@gmail.com>> wrote: >>> > >>> > well i can send you the image tommorow because its huge (200 MB ziped) >>> > for my pathetically slow internet connection at home. I will send it >>> > from work which is 8 times faster. >>> >>> If the image is 200 MB zipped, how large is it in its normal state ? >>> >>> For me, a 100 MB image file is already quite large, that would compress >>> to >>> maybe 20/30 MB. >>> >>> This doesn't sound right to me, unless you explicitly tried to store a >>> lot >>> of data. >>> >>> Maybe something else is wrong that would explain the slowness. >>> >>> > I can tell you that I am on MacOS Yosemite , I get my image with >>> > pharolauncher, the image was dowloaded at 27-07-15 some of the 84 >>> > items >>> > are folders that contain many sub folders. No idea if that matters. >>> > >>> > I got Roassal 2 using the Package Browser in Pharo 5 (the new >>> > configuration browser). >>> > >>> > On Wed, Jul 29, 2015 at 8:17 PM Alexandre Bergel >>> > <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >>> > Are you using windows? I know it may has problems regarding the source >>> > code. You have 84 items and the visualization is slow? How is this >>> > possible. >>> > >>> > Can I have a look at your image? >>> > >>> > Cheers, >>> > Alexandre >>> > -- >>> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> > Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >>> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> > >>> > >>> > >>> >> On Jul 29, 2015, at 12:26 PM, Dimitris Chloupis >>> >> <kilon.alios(a)gmail.com >>> >> <mailto:kilon.alios@gmail.com>> wrote: >>> >> >>> >> thats ok it unfroze after 20 minutes or so . I managed to inspect the >>> >> b >>> >> but its incredible slow to navigate and use . Even moving the >>> >> inspector >>> >> around is incredible slow. My Documents folder contains 84 items, >>> >> maybe >>> >> it cant handle so well this amount of datea ? >>> >> >>> >> On Wed, Jul 29, 2015 at 5:55 PM Alexandre Bergel >>> >> <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >>> >> Ohâ¦ sorry. Was not my intention >>> >> >>> >> Alexandre >>> >> -- >>> >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> >> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >>> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >> >>> >> >>> >> >>> >>> On Jul 29, 2015, at 11:24 AM, Dimitris Chloupis >>> >>> <kilon.alios(a)gmail.com >>> >>> <mailto:kilon.alios@gmail.com>> wrote: >>> >>> >>> >>> that was a nice way to freeze my image, thank you :D >>> >>> >>> >>> On Wed, Jul 29, 2015 at 4:27 PM Alexandre Bergel >>> >>> <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >>> >>> Hi! >>> >>> >>> >>> Just to share a couple of experiment. I have tried the following in >>> >>> a >>> >>> playground: >>> >>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >>> >>> b := RTMondrian new. >>> >>> >>> >>> b shape rectangle >>> >>> if: [ :aFile | aFile path basename beginsWith: '.' ] color: >>> >>> Color >>> >>> red. >>> >>> b nodes: FileLocator documents allChildren. >>> >>> b edges connectFrom: #parent. >>> >>> b normalizer >>> >>> normalizeSize: #size using: #sqrt. >>> >>> b layout tree. >>> >>> b >>> >>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >>> >>> >>> >>> It shows a tree of the file system. Thanks to GT, simply clicking on >>> >>> a >>> >>> file may show you the content and other things. >>> >>> <Screen Shot 2015-07-29 at 10.23.51 AM.png> >>> >>> >>> >>> You can also use the cluster layout: >>> >>> <Screen Shot 2015-07-29 at 10.25.11 AM.png> >>> >>> >>> >>> I have tried this on OS X, since the pointed folder is ~/Documents. >>> >>> >>> >>> Cheers, >>> >>> Alexandre >>> >>> -- >>> >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> >>> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >>> >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> >>> Moose-dev mailing list >>> >>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >>> >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >>> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >>> >> >>> >> _______________________________________________ >>> >> Moose-dev mailing list >>> >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >>> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >>> >> _______________________________________________ >>> >> Moose-dev mailing list >>> >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >>> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> >> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >>> > >>> > _______________________________________________ >>> > Moose-dev mailing list >>> > Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >>> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> > <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >>> > _______________________________________________ >>> > Moose-dev mailing list >>> > Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >>> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> > <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >>> >>> >>> >>> >>> -- >>> www.tudorgirba.com <http://www.tudorgirba.com/> >>> >>> "Every thing has its own flow" >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> > >

July 30, 2015

Re: [Pharo-users] interview on .Net Rocks! about Moose, humane assessment, Pharo and GT

by Tudor Girba

Hi, Indeed, GTSpotter, GTPlayground and GTInspector come with Pharo 4. The GTDebugger is available in the Moose 5/5.1/6.0 images. Thanks for the notification. I will update the page. Cheers, Doru On Thu, Jul 30, 2015 at 10:12 PM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > Doru, > > Thank you for the links > > Is the glamorous Toolkit preinstalled in Pharo 4? > > In any case > > http://gt.moosetechnology.org/ > > needs to mention Pharo 4. > > --Hannes > > On 7/30/15, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > > > I had the pleasure of giving an interview for the .Net Rocks! podcast. It > > was quite fun and I managed to mention Moose, humane assessment, Pharo > and > > GT in 45 minutes. It was not as smooth as a presentation but I still > think > > it's a useful advertisement. > > > > Let me know what you think, and feel free to promote it further: > > > > https://dotnetrocks.com/default.aspx?showNum=1172 > > > http://www.tudorgirba.com/blog/dotnetrocks-interview-moose-humane-assessmen… > > > > Cheers, > > Doru > > > > -- > > www.tudorgirba.com > > > > "Every thing has its own flow" > > > > -- www.tudorgirba.com "Every thing has its own flow"

July 30, 2015

Re: [Pharo-users] interview on .Net Rocks! about Moose, humane assessment, Pharo and GT

by H. Hirzel

Doru, Thank you for the links Is the glamorous Toolkit preinstalled in Pharo 4? In any case http://gt.moosetechnology.org/ needs to mention Pharo 4. --Hannes On 7/30/15, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I had the pleasure of giving an interview for the .Net Rocks! podcast. It > was quite fun and I managed to mention Moose, humane assessment, Pharo and > GT in 45 minutes. It was not as smooth as a presentation but I still think > it's a useful advertisement. > > Let me know what you think, and feel free to promote it further: > > https://dotnetrocks.com/default.aspx?showNum=1172 > http://www.tudorgirba.com/blog/dotnetrocks-interview-moose-humane-assessmen… > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

July 30, 2015

Re: [Pharo-users] interview on .Net Rocks! about Moose, humaneassessment, Pharo and GT

by Peter Uhnak

Thank you, I've really enjoyed it! Peter -----Original Message----- From: "Tudor Girba" <tudor(a)tudorgirba.com> Sent: â7/â30/â2015 9:35 PM To: "moose-dev" <moose-dev(a)iam.unibe.ch>; "Discusses Development of Pharo" <pharo-dev(a)lists.pharo.org>; "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> Subject: [Pharo-users] interview on .Net Rocks! about Moose, humaneassessment, Pharo and GT Hi, I had the pleasure of giving an interview for the .Net Rocks! podcast. It was quite fun and I managed to mention Moose, humane assessment, Pharo and GT in 45 minutes. It was not as smooth as a presentation but I still think it's a useful advertisement. Let me know what you think, and feel free to promote it further: https://dotnetrocks.com/default.aspx?showNum=1172 http://www.tudorgirba.com/blog/dotnetrocks-interview-moose-humane-assessmen… Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

July 30, 2015

Re: [Pharo-users] [Moose-dev] Re: Script of the day

by Peter Uhnak

You should be able to specify all layouts available in roassal... b layout tree. b layout cluster. b layout force. ... Peter -----Original Message----- From: "H. Hirzel" <hannes.hirzel(a)gmail.com> Sent: â7/â30/â2015 8:40 PM To: "Moose-related development" <moose-dev(a)iam.unibe.ch>; "pharo-users(a)lists.pharo.org" <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-users] [Moose-dev] Re: Script of the day Is it possible to use a tree map? --Hannes On 7/30/15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > I gave a try, and I did not find anything weird. > I guess your document folder contains many files, as Doru said > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >> On Jul 30, 2015, at 5:51 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> >> wrote: >> >> Frankly I dont mind big images or big data , neither I share the obsession >> to shrink things down to few mbs in a time that we are talking in TBs . >> >> Anyway you asked for the image and this is a link to it >> >> https://www.dropbox.com/s/wh1071xgoo54fq7/1%20Ephestos%2027-05-15.zip?dl=0 >> <https://www.dropbox.com/s/wh1071xgoo54fq7/1%20Ephestos%2027-05-15.zip?dl=0> >> >> I dont think you will find anything abnormal about it though. >> >> I was wondering whether it would worth the effort beyond the unit tests >> that check for behaviour of the code to have also benchmark tests that >> will have to pass specific standards so that specific method must perform >> under a strict timetable specific tasks, this way CI may alert not only >> unit tests that fail but also benchmarks that fail , automagically. >> >> Maybe some food for thought. >> >> Personally I am far more worried how much CPU Pharo consumes than how much >> RAM. >> >> On Wed, Jul 29, 2015 at 11:54 PM Peter UhnÃ¡k <i.uhnak(a)gmail.com >> <mailto:i.uhnak@gmail.com>> wrote: >> Not sure if there is any downside (I've been using it for a long time >> without problems), but image cleanup often does wonders for me. >> >> Moose image >> 410 MB => cleanup (World -> System -> Do Image Cleanup) => save => 237 >> MB >> and I even had situations where it went from ~600 MB to ~60 MB. >> (As to why my images are so massive... right now there are 19 windows >> opened inside most of them with opened roassal visualization... and I am >> saving like every five minutes... but that is just a guess.) >> >> But image cleanup is supposed to break things, so better to backup the >> folder first. >> Plus is cache really necessary? I mean it's a cache. .image + .changes >> should usually suffice. >> >> Peter >> >> On Wed, Jul 29, 2015 at 10:45 PM, Dimitris Chloupis <kilon.alios(a)gmail.com >> <mailto:kilon.alios@gmail.com>> wrote: >> Tudor I dont know if you received my message but I already answered that >> with this: >> >> "ah ok then its normal. Yes the structure is extensive, its 13 folders >> (the rest 71 are files some of them very big), I would not be surprised if >> each contains 100 files in its own subfolders." >> >> >> >> On Wed, Jul 29, 2015 at 11:30 PM Tudor Girba <tudor(a)tudorgirba.com >> <mailto:tudor@tudorgirba.com>> wrote: >> Hi, >> >> But, do you confirm that you have many files under the mentioned folder? >> >> Cheers, >> Doru >> >> >> >> On Wed, Jul 29, 2015 at 10:25 PM, Dimitris Chloupis <kilon.alios(a)gmail.com >> <mailto:kilon.alios@gmail.com>> wrote: >> the image is 180 mb, changes are another 15, there are several other >> folders that raise the total size to 250 mb, monticello-cache and >> github-cache prodominately. >> >> Hmm ok my bad, the size of the zip is 89 MB not 200 mb. Still will take me >> 1-2 hours to upload on this connection. So if you guys still need the >> image i can upload tommorow from work, though it seems my slow down is >> normal. >> >> Afterall I am sure you can test it yourselves on complex file structures >> to see if it has delays as long as 20 minutes. >> >> >> >> On Wed, Jul 29, 2015 at 11:01 PM Sven Van Caekenberghe <sven(a)stfx.eu >> <mailto:sven@stfx.eu>> wrote: >> >> > On 29 Jul 2015, at 21:33, Dimitris Chloupis <kilon.alios(a)gmail.com >> > <mailto:kilon.alios@gmail.com>> wrote: >> > >> > well i can send you the image tommorow because its huge (200 MB ziped) >> > for my pathetically slow internet connection at home. I will send it >> > from work which is 8 times faster. >> >> If the image is 200 MB zipped, how large is it in its normal state ? >> >> For me, a 100 MB image file is already quite large, that would compress to >> maybe 20/30 MB. >> >> This doesn't sound right to me, unless you explicitly tried to store a lot >> of data. >> >> Maybe something else is wrong that would explain the slowness. >> >> > I can tell you that I am on MacOS Yosemite , I get my image with >> > pharolauncher, the image was dowloaded at 27-07-15 some of the 84 items >> > are folders that contain many sub folders. No idea if that matters. >> > >> > I got Roassal 2 using the Package Browser in Pharo 5 (the new >> > configuration browser). >> > >> > On Wed, Jul 29, 2015 at 8:17 PM Alexandre Bergel >> > <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >> > Are you using windows? I know it may has problems regarding the source >> > code. You have 84 items and the visualization is slow? How is this >> > possible. >> > >> > Can I have a look at your image? >> > >> > Cheers, >> > Alexandre >> > -- >> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> > Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> > >> > >> > >> >> On Jul 29, 2015, at 12:26 PM, Dimitris Chloupis <kilon.alios(a)gmail.com >> >> <mailto:kilon.alios@gmail.com>> wrote: >> >> >> >> thats ok it unfroze after 20 minutes or so . I managed to inspect the b >> >> but its incredible slow to navigate and use . Even moving the inspector >> >> around is incredible slow. My Documents folder contains 84 items, maybe >> >> it cant handle so well this amount of datea ? >> >> >> >> On Wed, Jul 29, 2015 at 5:55 PM Alexandre Bergel >> >> <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >> >> Ohâ¦ sorry. Was not my intention >> >> >> >> Alexandre >> >> -- >> >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> >> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> >>> On Jul 29, 2015, at 11:24 AM, Dimitris Chloupis <kilon.alios(a)gmail.com >> >>> <mailto:kilon.alios@gmail.com>> wrote: >> >>> >> >>> that was a nice way to freeze my image, thank you :D >> >>> >> >>> On Wed, Jul 29, 2015 at 4:27 PM Alexandre Bergel >> >>> <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >> >>> Hi! >> >>> >> >>> Just to share a couple of experiment. I have tried the following in a >> >>> playground: >> >>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >> >>> b := RTMondrian new. >> >>> >> >>> b shape rectangle >> >>> if: [ :aFile | aFile path basename beginsWith: '.' ] color: Color >> >>> red. >> >>> b nodes: FileLocator documents allChildren. >> >>> b edges connectFrom: #parent. >> >>> b normalizer >> >>> normalizeSize: #size using: #sqrt. >> >>> b layout tree. >> >>> b >> >>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >> >>> >> >>> It shows a tree of the file system. Thanks to GT, simply clicking on a >> >>> file may show you the content and other things. >> >>> <Screen Shot 2015-07-29 at 10.23.51 AM.png> >> >>> >> >>> You can also use the cluster layout: >> >>> <Screen Shot 2015-07-29 at 10.25.11 AM.png> >> >>> >> >>> I have tried this on OS X, since the pointed folder is ~/Documents. >> >>> >> >>> Cheers, >> >>> Alexandre >> >>> -- >> >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> >>> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >> >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >>> >> >>> >> >>> >> >>> _______________________________________________ >> >>> Moose-dev mailing list >> >>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >>> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> >> >> >> _______________________________________________ >> >> Moose-dev mailing list >> >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> >> _______________________________________________ >> >> Moose-dev mailing list >> >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> > >> > _______________________________________________ >> > Moose-dev mailing list >> > Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> > _______________________________________________ >> > Moose-dev mailing list >> > Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> >> >> >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com/> >> >> "Every thing has its own flow" >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > >

July 30, 2015

Re: [Pharo-users] VM Crash after adding ram

by Nicolai Hess

Hm, I updated my Ubuntu 14.04 64 machine (just a normal update). Now I can not start any pharo vm. (not that one that from pharo launcher, no get.pharo.org/40 .. /50) ( they all were working some days ago). It crashes right after startup and not at the same call, the crash dumps show different stacktraces. Maybe a change from Ubuntu? 2015-07-30 20:27 GMT+02:00 Ramon Leon <ramon.leon(a)allresnet.com>: > So I've just upgraded my Ubuntu 14.04 machine to 16 gig of ram from 8 gig > of ram and suddenly I can no longer start my Pharo VM; I don't understand > why adding ram would make the vm stop working, I've been using it for year > without problems. Can anyone interpret this: > > no objects after the end of memory > > pharo VM version: 3.9-7 #1 Tue May 6 08:26:29 UTC 2014 gcc 4.8.1 > [Production ITHB VM] > Built from: NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: > acc98e51-2fba-4841-a965-2975997bba66 May 6 2014 > With: NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: > acc98e51-2fba-4841-a965-2975997bba66 May 6 2014 > Revision: https://github.com/pharo-project/pharo-vm.git Commit: > ef5832e6f70e5b24e8b9b1f4b8509a62b6c88040 Date: 2014-01-26 15:34:28 +0100 > By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14794 > Build host: Linux wani07 2.6.24-32-xen #1 SMP Mon Dec 3 16:12:25 UTC 2012 > i686 i686 i686 GNU/Linux > plugin path: /usr/lib/pharo-vm/ [default: /usr/lib/pharo-vm/] > > > C stack backtrace: > /usr/lib/pharo-vm/pharo-vm[0x809add3] > /usr/lib/pharo-vm/pharo-vm(error+0x17)[0x809af37] > /usr/lib/pharo-vm/pharo-vm[0x806ee94] > [0xb72ca6cd] > [0xb72b0700] > [0xb72ca2ca] > [0xb72b0ccd] > [0xb72b1989] > [0xb72b0c5b] > [0xb72b0700] > [0xb8080227] > [0xb807c7e1] > [0xb807ca01] > [0xb72b05c0] > > > Smalltalk stack dump: > 0xffa39fc8 M ExternalAddress class(Behavior)>allInstancesDo: 0xb86ca450: > a(n) ExternalAddress class > 0xffa39fec I ExternalAddress class>startUp: 0xb86ca450: a(n) > ExternalAddress class > 0xffa3a008 M ExternalObject class>startUp: 0xb86c8820: a(n) ExternalObject > class > 0xffa3a030 M [] in SmalltalkImage>send:toClassesNamedIn:with: 0xb75c4c24: > a(n) SmalltalkImage > 0xffa3a04c M BlockClosure>on:do: 0xc30bd160: a(n) BlockClosure > 0xffa3a07c M [] in SmalltalkImage>send:toClassesNamedIn:with: 0xb75c4c24: > a(n) SmalltalkImage > 0xffa3a0a4 I OrderedCollection>do: 0xb75c4d54: a(n) OrderedCollection > 0xffa3a0cc I SmalltalkImage>send:toClassesNamedIn:with: 0xb75c4c24: a(n) > SmalltalkImage > 0xffa3a0f8 I SmalltalkImage>processStartUpList: 0xb75c4c24: a(n) > SmalltalkImage > 0xffa3a124 I SmalltalkImage>snapshot:andQuit:embedded: 0xb75c4c24: a(n) > SmalltalkImage > 0xc26d5f90 s SmalltalkImage>snapshot:andQuit: > 0xc2bff710 s WorldState class>saveAndQuit > 0xc2bff76c s [] in ToggleMenuItemMorph(MenuItemMorph)>invokeWithEvent: > 0xc2bff7c8 s BlockClosure>ensure: > 0xc26d5114 s CursorWithMask(Cursor)>showWhile: > 0xc26d50a4 s ToggleMenuItemMorph(MenuItemMorph)>invokeWithEvent: > 0xc2bff824 s ToggleMenuItemMorph(MenuItemMorph)>mouseUp: > 0xc2bff880 s ToggleMenuItemMorph(MenuItemMorph)>handleMouseUp: > 0xc2bff8dc s MouseButtonEvent>sentTo: > 0xc2bff938 s ToggleMenuItemMorph(Morph)>handleEvent: > 0xc26d4f80 s MorphicEventDispatcher>dispatchDefault:with: > 0xc26d4fdc s MorphicEventDispatcher>dispatchEvent:with: > 0xc2bfefe0 s ToggleMenuItemMorph(Morph)>processEvent:using: > 0xc2bff03c s MorphicEventDispatcher>dispatchDefault:with: > 0xc2bff098 s MorphicEventDispatcher>dispatchEvent:with: > 0xc2bff0f4 s MenuMorph(Morph)>processEvent:using: > 0xc2bff150 s MenuMorph(Morph)>processEvent: > 0xc2bff1ac s MenuMorph>handleFocusEvent: > 0xc2bff208 s [] in HandMorph>sendFocusEvent:to:clear: > 0xc2bff264 s [] in PasteUpMorph>becomeActiveDuring: > 0xc2bff2c0 s BlockClosure>on:do: > 0xc26d4e8c s PasteUpMorph>becomeActiveDuring: > 0xc26d4e14 s HandMorph>sendFocusEvent:to:clear: > 0xc2bff9f0 s HandMorph>sendEvent:focus:clear: > 0xc26d4da0 s HandMorph>sendMouseEvent: > 0xc26d4d38 s HandMorph>handleEvent: > 0xc2bffa4c s HandMorph>processEvents > 0xc2bffaa8 s [] in WorldState>doOneCycleNowFor: > 0xc2bffb04 s Array(SequenceableCollection)>do: > 0xc2bffb60 s WorldState>handsDo: > 0xc26d4bd4 s WorldState>doOneCycleNowFor: > 0xc2bffbbc s WorldState>doOneCycleFor: > 0xc2bffc18 s PasteUpMorph>doOneCycle > 0xc240332c s [] in Project class>spawnNewProcess > 0xc2403078 s [] in BlockClosure>newProcess > > Most recent primitives > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > < > basicNew: > findSubstringViaPrimitive:in:startingAt:matchTable: > new: > basicNew > new: > at:put: > at:put: > perform:with: > perform:with: > at: > at: > perform:with: > perform:with: > someInstance > nextInstance > millisecondClockValue > signal > at:put: > at:put: > primSignal:atMilliseconds: > millisecondClockValue > wait > primGetNextEvent: > millisecondClockValue > wait > signal > at:put: > at:put: > millisecondClockValue > primSignal:atMilliseconds: > millisecondClockValue > wait > signal > wait > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > > stack page bytes 4096 available headroom 3300 minimum unused headroom 3540 > > (no objects after the end of memory) > Aborted (core dumped) > > -- > Ramon Leon > > >

July 30, 2015

interview on .Net Rocks! about Moose, humane assessment, Pharo and GT

by Tudor Girba

Hi, I had the pleasure of giving an interview for the .Net Rocks! podcast. It was quite fun and I managed to mention Moose, humane assessment, Pharo and GT in 45 minutes. It was not as smooth as a presentation but I still think it's a useful advertisement. Let me know what you think, and feel free to promote it further: https://dotnetrocks.com/default.aspx?showNum=1172 http://www.tudorgirba.com/blog/dotnetrocks-interview-moose-humane-assessmen… Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

July 30, 2015

Re: [Pharo-users] VM Crash after adding ram

by Esteban Lorenzano

Hi, did you try a fresh Pharo image (without loaded code)? ExternalObject and ExternalAddress are FFI soâ¦ problem *could* be thereâ¦ no idea what can be happening, but wellâ¦ it could be there :) cheers, Esteban > On 30 Jul 2015, at 20:27, Ramon Leon <ramon.leon(a)allresnet.com> wrote: > > So I've just upgraded my Ubuntu 14.04 machine to 16 gig of ram from 8 gig of ram and suddenly I can no longer start my Pharo VM; I don't understand why adding ram would make the vm stop working, I've been using it for year without problems. Can anyone interpret this: > > no objects after the end of memory > > pharo VM version: 3.9-7 #1 Tue May 6 08:26:29 UTC 2014 gcc 4.8.1 [Production ITHB VM] > Built from: NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 May 6 2014 > With: NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 May 6 2014 > Revision: https://github.com/pharo-project/pharo-vm.git Commit: ef5832e6f70e5b24e8b9b1f4b8509a62b6c88040 Date: 2014-01-26 15:34:28 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14794 > Build host: Linux wani07 2.6.24-32-xen #1 SMP Mon Dec 3 16:12:25 UTC 2012 i686 i686 i686 GNU/Linux > plugin path: /usr/lib/pharo-vm/ [default: /usr/lib/pharo-vm/] > > > C stack backtrace: > /usr/lib/pharo-vm/pharo-vm[0x809add3] > /usr/lib/pharo-vm/pharo-vm(error+0x17)[0x809af37] > /usr/lib/pharo-vm/pharo-vm[0x806ee94] > [0xb72ca6cd] > [0xb72b0700] > [0xb72ca2ca] > [0xb72b0ccd] > [0xb72b1989] > [0xb72b0c5b] > [0xb72b0700] > [0xb8080227] > [0xb807c7e1] > [0xb807ca01] > [0xb72b05c0] > > > Smalltalk stack dump: > 0xffa39fc8 M ExternalAddress class(Behavior)>allInstancesDo: 0xb86ca450: a(n) ExternalAddress class > 0xffa39fec I ExternalAddress class>startUp: 0xb86ca450: a(n) ExternalAddress class > 0xffa3a008 M ExternalObject class>startUp: 0xb86c8820: a(n) ExternalObject class > 0xffa3a030 M [] in SmalltalkImage>send:toClassesNamedIn:with: 0xb75c4c24: a(n) SmalltalkImage > 0xffa3a04c M BlockClosure>on:do: 0xc30bd160: a(n) BlockClosure > 0xffa3a07c M [] in SmalltalkImage>send:toClassesNamedIn:with: 0xb75c4c24: a(n) SmalltalkImage > 0xffa3a0a4 I OrderedCollection>do: 0xb75c4d54: a(n) OrderedCollection > 0xffa3a0cc I SmalltalkImage>send:toClassesNamedIn:with: 0xb75c4c24: a(n) SmalltalkImage > 0xffa3a0f8 I SmalltalkImage>processStartUpList: 0xb75c4c24: a(n) SmalltalkImage > 0xffa3a124 I SmalltalkImage>snapshot:andQuit:embedded: 0xb75c4c24: a(n) SmalltalkImage > 0xc26d5f90 s SmalltalkImage>snapshot:andQuit: > 0xc2bff710 s WorldState class>saveAndQuit > 0xc2bff76c s [] in ToggleMenuItemMorph(MenuItemMorph)>invokeWithEvent: > 0xc2bff7c8 s BlockClosure>ensure: > 0xc26d5114 s CursorWithMask(Cursor)>showWhile: > 0xc26d50a4 s ToggleMenuItemMorph(MenuItemMorph)>invokeWithEvent: > 0xc2bff824 s ToggleMenuItemMorph(MenuItemMorph)>mouseUp: > 0xc2bff880 s ToggleMenuItemMorph(MenuItemMorph)>handleMouseUp: > 0xc2bff8dc s MouseButtonEvent>sentTo: > 0xc2bff938 s ToggleMenuItemMorph(Morph)>handleEvent: > 0xc26d4f80 s MorphicEventDispatcher>dispatchDefault:with: > 0xc26d4fdc s MorphicEventDispatcher>dispatchEvent:with: > 0xc2bfefe0 s ToggleMenuItemMorph(Morph)>processEvent:using: > 0xc2bff03c s MorphicEventDispatcher>dispatchDefault:with: > 0xc2bff098 s MorphicEventDispatcher>dispatchEvent:with: > 0xc2bff0f4 s MenuMorph(Morph)>processEvent:using: > 0xc2bff150 s MenuMorph(Morph)>processEvent: > 0xc2bff1ac s MenuMorph>handleFocusEvent: > 0xc2bff208 s [] in HandMorph>sendFocusEvent:to:clear: > 0xc2bff264 s [] in PasteUpMorph>becomeActiveDuring: > 0xc2bff2c0 s BlockClosure>on:do: > 0xc26d4e8c s PasteUpMorph>becomeActiveDuring: > 0xc26d4e14 s HandMorph>sendFocusEvent:to:clear: > 0xc2bff9f0 s HandMorph>sendEvent:focus:clear: > 0xc26d4da0 s HandMorph>sendMouseEvent: > 0xc26d4d38 s HandMorph>handleEvent: > 0xc2bffa4c s HandMorph>processEvents > 0xc2bffaa8 s [] in WorldState>doOneCycleNowFor: > 0xc2bffb04 s Array(SequenceableCollection)>do: > 0xc2bffb60 s WorldState>handsDo: > 0xc26d4bd4 s WorldState>doOneCycleNowFor: > 0xc2bffbbc s WorldState>doOneCycleFor: > 0xc2bffc18 s PasteUpMorph>doOneCycle > 0xc240332c s [] in Project class>spawnNewProcess > 0xc2403078 s [] in BlockClosure>newProcess > > Most recent primitives > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > at:put: > < > basicNew: > findSubstringViaPrimitive:in:startingAt:matchTable: > new: > basicNew > new: > at:put: > at:put: > perform:with: > perform:with: > at: > at: > perform:with: > perform:with: > someInstance > nextInstance > millisecondClockValue > signal > at:put: > at:put: > primSignal:atMilliseconds: > millisecondClockValue > wait > primGetNextEvent: > millisecondClockValue > wait > signal > at:put: > at:put: > millisecondClockValue > primSignal:atMilliseconds: > millisecondClockValue > wait > signal > wait > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > atAllPut: > nextInstance > > stack page bytes 4096 available headroom 3300 minimum unused headroom 3540 > > (no objects after the end of memory) > Aborted (core dumped) > > -- > Ramon Leon > >

July 30, 2015

Re: [Pharo-users] [Moose-dev] Re: Script of the day

by H. Hirzel

Is it possible to use a tree map? --Hannes On 7/30/15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > I gave a try, and I did not find anything weird. > I guess your document folder contains many files, as Doru said > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >> On Jul 30, 2015, at 5:51 AM, Dimitris Chloupis <kilon.alios(a)gmail.com> >> wrote: >> >> Frankly I dont mind big images or big data , neither I share the obsession >> to shrink things down to few mbs in a time that we are talking in TBs . >> >> Anyway you asked for the image and this is a link to it >> >> https://www.dropbox.com/s/wh1071xgoo54fq7/1%20Ephestos%2027-05-15.zip?dl=0 >> <https://www.dropbox.com/s/wh1071xgoo54fq7/1%20Ephestos%2027-05-15.zip?dl=0> >> >> I dont think you will find anything abnormal about it though. >> >> I was wondering whether it would worth the effort beyond the unit tests >> that check for behaviour of the code to have also benchmark tests that >> will have to pass specific standards so that specific method must perform >> under a strict timetable specific tasks, this way CI may alert not only >> unit tests that fail but also benchmarks that fail , automagically. >> >> Maybe some food for thought. >> >> Personally I am far more worried how much CPU Pharo consumes than how much >> RAM. >> >> On Wed, Jul 29, 2015 at 11:54 PM Peter UhnÃ¡k <i.uhnak(a)gmail.com >> <mailto:i.uhnak@gmail.com>> wrote: >> Not sure if there is any downside (I've been using it for a long time >> without problems), but image cleanup often does wonders for me. >> >> Moose image >> 410 MB => cleanup (World -> System -> Do Image Cleanup) => save => 237 >> MB >> and I even had situations where it went from ~600 MB to ~60 MB. >> (As to why my images are so massive... right now there are 19 windows >> opened inside most of them with opened roassal visualization... and I am >> saving like every five minutes... but that is just a guess.) >> >> But image cleanup is supposed to break things, so better to backup the >> folder first. >> Plus is cache really necessary? I mean it's a cache. .image + .changes >> should usually suffice. >> >> Peter >> >> On Wed, Jul 29, 2015 at 10:45 PM, Dimitris Chloupis <kilon.alios(a)gmail.com >> <mailto:kilon.alios@gmail.com>> wrote: >> Tudor I dont know if you received my message but I already answered that >> with this: >> >> "ah ok then its normal. Yes the structure is extensive, its 13 folders >> (the rest 71 are files some of them very big), I would not be surprised if >> each contains 100 files in its own subfolders." >> >> >> >> On Wed, Jul 29, 2015 at 11:30 PM Tudor Girba <tudor(a)tudorgirba.com >> <mailto:tudor@tudorgirba.com>> wrote: >> Hi, >> >> But, do you confirm that you have many files under the mentioned folder? >> >> Cheers, >> Doru >> >> >> >> On Wed, Jul 29, 2015 at 10:25 PM, Dimitris Chloupis <kilon.alios(a)gmail.com >> <mailto:kilon.alios@gmail.com>> wrote: >> the image is 180 mb, changes are another 15, there are several other >> folders that raise the total size to 250 mb, monticello-cache and >> github-cache prodominately. >> >> Hmm ok my bad, the size of the zip is 89 MB not 200 mb. Still will take me >> 1-2 hours to upload on this connection. So if you guys still need the >> image i can upload tommorow from work, though it seems my slow down is >> normal. >> >> Afterall I am sure you can test it yourselves on complex file structures >> to see if it has delays as long as 20 minutes. >> >> >> >> On Wed, Jul 29, 2015 at 11:01 PM Sven Van Caekenberghe <sven(a)stfx.eu >> <mailto:sven@stfx.eu>> wrote: >> >> > On 29 Jul 2015, at 21:33, Dimitris Chloupis <kilon.alios(a)gmail.com >> > <mailto:kilon.alios@gmail.com>> wrote: >> > >> > well i can send you the image tommorow because its huge (200 MB ziped) >> > for my pathetically slow internet connection at home. I will send it >> > from work which is 8 times faster. >> >> If the image is 200 MB zipped, how large is it in its normal state ? >> >> For me, a 100 MB image file is already quite large, that would compress to >> maybe 20/30 MB. >> >> This doesn't sound right to me, unless you explicitly tried to store a lot >> of data. >> >> Maybe something else is wrong that would explain the slowness. >> >> > I can tell you that I am on MacOS Yosemite , I get my image with >> > pharolauncher, the image was dowloaded at 27-07-15 some of the 84 items >> > are folders that contain many sub folders. No idea if that matters. >> > >> > I got Roassal 2 using the Package Browser in Pharo 5 (the new >> > configuration browser). >> > >> > On Wed, Jul 29, 2015 at 8:17 PM Alexandre Bergel >> > <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >> > Are you using windows? I know it may has problems regarding the source >> > code. You have 84 items and the visualization is slow? How is this >> > possible. >> > >> > Can I have a look at your image? >> > >> > Cheers, >> > Alexandre >> > -- >> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> > Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> > >> > >> > >> >> On Jul 29, 2015, at 12:26 PM, Dimitris Chloupis <kilon.alios(a)gmail.com >> >> <mailto:kilon.alios@gmail.com>> wrote: >> >> >> >> thats ok it unfroze after 20 minutes or so . I managed to inspect the b >> >> but its incredible slow to navigate and use . Even moving the inspector >> >> around is incredible slow. My Documents folder contains 84 items, maybe >> >> it cant handle so well this amount of datea ? >> >> >> >> On Wed, Jul 29, 2015 at 5:55 PM Alexandre Bergel >> >> <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >> >> Ohâ¦ sorry. Was not my intention >> >> >> >> Alexandre >> >> -- >> >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> >> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> >>> On Jul 29, 2015, at 11:24 AM, Dimitris Chloupis <kilon.alios(a)gmail.com >> >>> <mailto:kilon.alios@gmail.com>> wrote: >> >>> >> >>> that was a nice way to freeze my image, thank you :D >> >>> >> >>> On Wed, Jul 29, 2015 at 4:27 PM Alexandre Bergel >> >>> <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >> >>> Hi! >> >>> >> >>> Just to share a couple of experiment. I have tried the following in a >> >>> playground: >> >>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >> >>> b := RTMondrian new. >> >>> >> >>> b shape rectangle >> >>> if: [ :aFile | aFile path basename beginsWith: '.' ] color: Color >> >>> red. >> >>> b nodes: FileLocator documents allChildren. >> >>> b edges connectFrom: #parent. >> >>> b normalizer >> >>> normalizeSize: #size using: #sqrt. >> >>> b layout tree. >> >>> b >> >>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >> >>> >> >>> It shows a tree of the file system. Thanks to GT, simply clicking on a >> >>> file may show you the content and other things. >> >>> <Screen Shot 2015-07-29 at 10.23.51 AM.png> >> >>> >> >>> You can also use the cluster layout: >> >>> <Screen Shot 2015-07-29 at 10.25.11 AM.png> >> >>> >> >>> I have tried this on OS X, since the pointed folder is ~/Documents. >> >>> >> >>> Cheers, >> >>> Alexandre >> >>> -- >> >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> >>> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >> >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >>> >> >>> >> >>> >> >>> _______________________________________________ >> >>> Moose-dev mailing list >> >>> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >>> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> >> >> >> _______________________________________________ >> >> Moose-dev mailing list >> >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> >> _______________________________________________ >> >> Moose-dev mailing list >> >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> > >> > _______________________________________________ >> > Moose-dev mailing list >> > Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> > _______________________________________________ >> > Moose-dev mailing list >> > Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> > https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> >> >> >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com/> >> >> "Every thing has its own flow" >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch <mailto:Moose-dev@iam.unibe.ch> >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> <https://www.iam.unibe.ch/mailman/listinfo/moose-dev> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > >

July 30, 2015

VM Crash after adding ram

by Ramon Leon

So I've just upgraded my Ubuntu 14.04 machine to 16 gig of ram from 8 gig of ram and suddenly I can no longer start my Pharo VM; I don't understand why adding ram would make the vm stop working, I've been using it for year without problems. Can anyone interpret this: no objects after the end of memory pharo VM version: 3.9-7 #1 Tue May 6 08:26:29 UTC 2014 gcc 4.8.1 [Production ITHB VM] Built from: NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 May 6 2014 With: NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 May 6 2014 Revision: https://github.com/pharo-project/pharo-vm.git Commit: ef5832e6f70e5b24e8b9b1f4b8509a62b6c88040 Date: 2014-01-26 15:34:28 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14794 Build host: Linux wani07 2.6.24-32-xen #1 SMP Mon Dec 3 16:12:25 UTC 2012 i686 i686 i686 GNU/Linux plugin path: /usr/lib/pharo-vm/ [default: /usr/lib/pharo-vm/] C stack backtrace: /usr/lib/pharo-vm/pharo-vm[0x809add3] /usr/lib/pharo-vm/pharo-vm(error+0x17)[0x809af37] /usr/lib/pharo-vm/pharo-vm[0x806ee94] [0xb72ca6cd] [0xb72b0700] [0xb72ca2ca] [0xb72b0ccd] [0xb72b1989] [0xb72b0c5b] [0xb72b0700] [0xb8080227] [0xb807c7e1] [0xb807ca01] [0xb72b05c0] Smalltalk stack dump: 0xffa39fc8 M ExternalAddress class(Behavior)>allInstancesDo: 0xb86ca450: a(n) ExternalAddress class 0xffa39fec I ExternalAddress class>startUp: 0xb86ca450: a(n) ExternalAddress class 0xffa3a008 M ExternalObject class>startUp: 0xb86c8820: a(n) ExternalObject class 0xffa3a030 M [] in SmalltalkImage>send:toClassesNamedIn:with: 0xb75c4c24: a(n) SmalltalkImage 0xffa3a04c M BlockClosure>on:do: 0xc30bd160: a(n) BlockClosure 0xffa3a07c M [] in SmalltalkImage>send:toClassesNamedIn:with: 0xb75c4c24: a(n) SmalltalkImage 0xffa3a0a4 I OrderedCollection>do: 0xb75c4d54: a(n) OrderedCollection 0xffa3a0cc I SmalltalkImage>send:toClassesNamedIn:with: 0xb75c4c24: a(n) SmalltalkImage 0xffa3a0f8 I SmalltalkImage>processStartUpList: 0xb75c4c24: a(n) SmalltalkImage 0xffa3a124 I SmalltalkImage>snapshot:andQuit:embedded: 0xb75c4c24: a(n) SmalltalkImage 0xc26d5f90 s SmalltalkImage>snapshot:andQuit: 0xc2bff710 s WorldState class>saveAndQuit 0xc2bff76c s [] in ToggleMenuItemMorph(MenuItemMorph)>invokeWithEvent: 0xc2bff7c8 s BlockClosure>ensure: 0xc26d5114 s CursorWithMask(Cursor)>showWhile: 0xc26d50a4 s ToggleMenuItemMorph(MenuItemMorph)>invokeWithEvent: 0xc2bff824 s ToggleMenuItemMorph(MenuItemMorph)>mouseUp: 0xc2bff880 s ToggleMenuItemMorph(MenuItemMorph)>handleMouseUp: 0xc2bff8dc s MouseButtonEvent>sentTo: 0xc2bff938 s ToggleMenuItemMorph(Morph)>handleEvent: 0xc26d4f80 s MorphicEventDispatcher>dispatchDefault:with: 0xc26d4fdc s MorphicEventDispatcher>dispatchEvent:with: 0xc2bfefe0 s ToggleMenuItemMorph(Morph)>processEvent:using: 0xc2bff03c s MorphicEventDispatcher>dispatchDefault:with: 0xc2bff098 s MorphicEventDispatcher>dispatchEvent:with: 0xc2bff0f4 s MenuMorph(Morph)>processEvent:using: 0xc2bff150 s MenuMorph(Morph)>processEvent: 0xc2bff1ac s MenuMorph>handleFocusEvent: 0xc2bff208 s [] in HandMorph>sendFocusEvent:to:clear: 0xc2bff264 s [] in PasteUpMorph>becomeActiveDuring: 0xc2bff2c0 s BlockClosure>on:do: 0xc26d4e8c s PasteUpMorph>becomeActiveDuring: 0xc26d4e14 s HandMorph>sendFocusEvent:to:clear: 0xc2bff9f0 s HandMorph>sendEvent:focus:clear: 0xc26d4da0 s HandMorph>sendMouseEvent: 0xc26d4d38 s HandMorph>handleEvent: 0xc2bffa4c s HandMorph>processEvents 0xc2bffaa8 s [] in WorldState>doOneCycleNowFor: 0xc2bffb04 s Array(SequenceableCollection)>do: 0xc2bffb60 s WorldState>handsDo: 0xc26d4bd4 s WorldState>doOneCycleNowFor: 0xc2bffbbc s WorldState>doOneCycleFor: 0xc2bffc18 s PasteUpMorph>doOneCycle 0xc240332c s [] in Project class>spawnNewProcess 0xc2403078 s [] in BlockClosure>newProcess Most recent primitives at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: at:put: < basicNew: findSubstringViaPrimitive:in:startingAt:matchTable: new: basicNew new: at:put: at:put: perform:with: perform:with: at: at: perform:with: perform:with: someInstance nextInstance millisecondClockValue signal at:put: at:put: primSignal:atMilliseconds: millisecondClockValue wait primGetNextEvent: millisecondClockValue wait signal at:put: at:put: millisecondClockValue primSignal:atMilliseconds: millisecondClockValue wait signal wait atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance atAllPut: nextInstance stack page bytes 4096 available headroom 3300 minimum unused headroom 3540 (no objects after the end of memory) Aborted (core dumped) -- Ramon Leon

July 30, 2015