June 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Bloated image again. Memory leak?

by Esteban Lorenzano

> On 20 Jun 2017, at 08:16, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > What is the more general problem esteban? what *was* the general problem: there was a leak on glamour :) Esteban > > On Mon, Jun 19, 2017 at 12:10 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> On 19 Jun 2017, at 11:52, Davide Varvello via Pharo-users >> <pharo-users(a)lists.pharo.org> wrote: >> >> >> From: Davide Varvello <varvello(a)yahoo.com> >> Subject: Re: Bloated image again. Memory leak? >> Date: 19 June 2017 at 11:52:08 GMT+2 >> To: pharo-users(a)lists.pharo.org >> >> >> Thank you very much Phil, >> Your code works! The image went from 600MB to 80MB >> >> I'm wondering why there is no bug record about GLMPanePort on >> https://pharo.fogbugz.com/f/search/?sSearchFor=GLMPanePort nor a fix. Nobody >> has this issue, but you and me? I'm puzzled. >> >> >> I think because this was a more general bug that *should* be fixed on Pharo >> 6. >> >> cheers! >> Esteban >> >> >> Anyway >> Thank you very much >> Davide >> >> >> philippeback wrote >> >> Check >> >> https://gist.github.com/philippeback/39c63bb5aa26b79098511cdfea4fea7e >> >> Phil >> >> On Mon, Jun 19, 2017 at 8:45 AM, Davide Varvello via Pharo-users < >> >> >> pharo-users@.pharo >> >> >> wrote: >> >> >> >> >> ---------- Forwarded message ---------- >> From: Davide Varvello < >> >> >> varvello@ >> >> >> > >> >> To: >> >> >> pharo-users@.pharo >> >> >> Cc: >> Bcc: >> Date: Sun, 18 Jun 2017 23:45:32 -0700 (PDT) >> Subject: Bloated image again. Memory leak? >> Hi guys, >> I have this problem (http://forum.world.st/Huge-image-td4876854.html) >> now >> the image grow about 100MB per week and the suggestions shown on >> http://forum.world.st/Huge-image-td4876854.html don't work >> >> I'm on Pharo 5 on a mac. >> >> I suspect it is something related to GLMPanePort, see the attached jpg >> Can you help me please? >> >> TIA >> Davide >> >> >> <http://forum.world.st/file/n4951861/huge_image2.jpg> >> >> >> >> -- >> View this message in context: http://forum.world.st/Bloated- >> image-again-Memory-leak-tp4951861.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> >> >> >> >> >> >> >> >> -- >> View this message in context: >> http://forum.world.st/Bloated-image-again-Memory-leak-tp4951862p4951885.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> >

June 20, 2017

Re: [Pharo-users] Saving to local git and "Loading all file names from http://...pharo5/inbox"

by Stephane Ducasse

Ahh tx I understand now. I can tell you that I'm eager to do integration with git to avoid to get MC checking all the repo from earth and merging :) Stef On Mon, Jun 19, 2017 at 1:09 PM, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > Hi, > > there was an issue with presumably gitfiletree, that when checking a code against its repo (to commit or show changes), every single repository would be refreshed, which took quite a while (on the order of seconds to tens of seconds, but it was quite annoying as it happened frequently).. so as I don't need the repos unless I am fixing the bug, I removed them... > > I don't use it in Pharo 6 as I haven't experienced the issue there, but I am using Iceberg now, so maybe that is the reason. > > Peter > > > On Sat, Jun 17, 2017 at 03:19:41AM -0700, webwarrior wrote: >> Well, that is the question to the author of original script - Peter Uhnak. >> >> The goal is to avoid contacting server (takes alot of time and blocks the >> image) every time you save a package to a filetree repo. As I understand >> repositories in question are kind of special and are always checked, so >> removing them solves the problem. >> >> I just modified it to work on Pharo6. >> >> >> >> -- >> View this message in context: http://forum.world.st/Saving-to-local-git-and-Loading-all-file-names-from-h… >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >

June 20, 2017

Re: [Pharo-users] WrapAthen, World coordinate?

by Stephane Ducasse

:( Hi nicolai I really hope that github support and bootstrap will help for that With the bootstrap we are reloading code so we should reload Athens from the Pharo folder and people will be able to load this code too. For now I would consider that the code in the image is the latest "working" one. Does it make sense? Stef On Mon, Jun 19, 2017 at 8:53 AM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > Done: > > 20166 wrong cliprect on transformed athens canvas > > Although I don't know how we handle fixes for Athens, as the current > repository and in-image version already diverged again. > > > > 2017-06-19 8:15 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> >> Hi hilaire >> >> Can you add a bug entry in the pharo bug tracker? >> We cannot look at bugs that are not listed there. >> >> Stef >> >> On Sun, Jun 18, 2017 at 4:11 PM, Hilaire <hilaire(a)drgeo.eu> wrote: >> > Only the picture I sent previously, but Nicolas tracked the problem in >> > the clipping default choices: >> > >> > https://bugs.launchpad.net/drgeo/+bug/1698582 >> > >> > Le 18/06/2017 Ã 15:41, Stephane Ducasse a Ã©crit : >> >> Do you have an expression showing the problem? >> > >> > -- >> > Dr. Geo >> > http://drgeo.eu >> > >> > >> >

June 20, 2017

Re: [Pharo-users] Bloated image again. Memory leak?

by Stephane Ducasse

What is the more general problem esteban? On Mon, Jun 19, 2017 at 12:10 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On 19 Jun 2017, at 11:52, Davide Varvello via Pharo-users > <pharo-users(a)lists.pharo.org> wrote: > > > From: Davide Varvello <varvello(a)yahoo.com> > Subject: Re: Bloated image again. Memory leak? > Date: 19 June 2017 at 11:52:08 GMT+2 > To: pharo-users(a)lists.pharo.org > > > Thank you very much Phil, > Your code works! The image went from 600MB to 80MB > > I'm wondering why there is no bug record about GLMPanePort on > https://pharo.fogbugz.com/f/search/?sSearchFor=GLMPanePort nor a fix. Nobody > has this issue, but you and me? I'm puzzled. > > > I think because this was a more general bug that *should* be fixed on Pharo > 6. > > cheers! > Esteban > > > Anyway > Thank you very much > Davide > > > philippeback wrote > > Check > > https://gist.github.com/philippeback/39c63bb5aa26b79098511cdfea4fea7e > > Phil > > On Mon, Jun 19, 2017 at 8:45 AM, Davide Varvello via Pharo-users < > > > pharo-users@.pharo > > > wrote: > > > > > ---------- Forwarded message ---------- > From: Davide Varvello < > > > varvello@ > > > > > > To: > > > pharo-users@.pharo > > > Cc: > Bcc: > Date: Sun, 18 Jun 2017 23:45:32 -0700 (PDT) > Subject: Bloated image again. Memory leak? > Hi guys, > I have this problem (http://forum.world.st/Huge-image-td4876854.html) > now > the image grow about 100MB per week and the suggestions shown on > http://forum.world.st/Huge-image-td4876854.html don't work > > I'm on Pharo 5 on a mac. > > I suspect it is something related to GLMPanePort, see the attached jpg > Can you help me please? > > TIA > Davide > > > <http://forum.world.st/file/n4951861/huge_image2.jpg> > > > > -- > View this message in context: http://forum.world.st/Bloated- > image-again-Memory-leak-tp4951861.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > > > > > > > > > -- > View this message in context: > http://forum.world.st/Bloated-image-again-Memory-leak-tp4951862p4951885.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

June 20, 2017

Re: [Pharo-users] Finding files in Pharo

by Alistair Grant

Hi Hernan, On Mon, Jun 19, 2017 at 09:23:35PM -0300, Hern??n Morales Durand wrote: > I took the time to review FileSystemDirectoryEntry. > > UNIX has 3 types of timestamps > > -The access time is the last time when the content was accessed. > -The modification time is last time when the content was modified. > -The change time is the last time when the metadata was modified. > > FileSystemDirectoryEntry>>creationTime > This is wrong because there is no such thing as creation time in UNIX. Several linux file systems do support creation time, called birth time, but my understanding is that there is no standard way to retrieve the birth time commonly available and cross platform. > I checked in Linux chmod'ing an empty file and #creationTime displays the chmod > "change time". > Then added content to the file > > echo prueba >> test1.txt > > And both "creation" and "modification" instance variables were updated. > > I couldn't find #accessTime method to get the last timestamp of last access. Linux kernel 4.11 introduced statx(), which adds creation time, but I don't know if it will be adopted by BSD or MacOS. The patches I mentioned earlier and plan for Pharo 7 add support for all 4 timestamps (creation, change, modification, access). Which fields get populated depends on the platform. There's a #hasCreationTime flag which allows you to distinguish between the real creation time and the change time. Cheers, Alistair

June 20, 2017

Re: [Pharo-users] Regression with PNGReaderWriter in P6

by Stephane Ducasse

Thx guys! We will tag it for a port back to Pharo60. On Tue, Jun 20, 2017 at 5:05 AM, Ben Coman <btc(a)openinworld.com> wrote: > > On Mon, Jun 19, 2017 at 8:00 PM, David T. Lewis <lewis(a)mail.msen.com> wrote: >> >> 20167 > > > Thanks Dave. I've cherry-picked those into an integration slice, but I > don't have 64-bit to test on. > @Hilaire, could you test the slice? > > cheers -ben

June 20, 2017

Re: [Pharo-users] Regression with PNGReaderWriter in P6

by Ben Coman

On Mon, Jun 19, 2017 at 8:00 PM, David T. Lewis <lewis(a)mail.msen.com> wrote: > 20167 Thanks Dave. I've cherry-picked those into an integration slice, but I don't have 64-bit to test on. @Hilaire, could you test the slice? cheers -ben

June 20, 2017

Re: [Pharo-users] Anonymous classes performances

by Ben Coman

@all, Is there some way to disable garbage collection during such benchmarks? cheers -ben On Sun, Jun 18, 2017 at 3:51 AM, Steven Costiou <steven.costiou(a)kloum.io> wrote: > I spent my day testing and comparing execution speed between classes and > anonymous subclasses when i tried to compare two sets of values between > pharo classes: they also differ. > > In fact it seems that every instruction has a different execution speed if > we run it enough times. So it seems impossible to precisely compare > execution time between anon classes and pharo classes, at least i don't > know how to do it. I computed confidence intervals of various measures, the > differences in execution time that exist between classes and anonymous > classes can be between -2% to + 9%. But comparing sets of speed between > pharo classes, i also have similar intervals (but smaller, from -2% speed > to +5% speed). > > > > So maybe they have similar performances, at least sometimes they do and > sometimes one is slightly faster than the other, but in the end it is not > possible to tell. But maybe i'm looking for something which does not even > exist, maybe anonymous classes are designed to be as fast as regular > classes ? Or maybe it is common to have such variability when benchmarking > code ? > > > > Does it exist any instruction in pharo with a constant execution time ? > (or it could be possible with one million years to compute enough speed > tests and do an accurate mean...) > > > > Steven. > > > > Le 2017-06-16 18:14, Steven Costiou a Ã©crit : > > You can find the code below. I just change the call to m by m1 to test the > two methods. > > I started again in a fresh pharo 6 image and now the results seem all > similar for the following code. I will do all my tests again to see if it > was my fault but it takes a lot of time (2 hours for each full test). > > What sould be the expected results ? Should an instance of an anonymous > class be as fast as a regular instance when calling the same code, being > defined in the anon class or its super class ? > > > > A implements m ^100 printString and B subclass of A implements m1 ^100 > printString > > a := B new. > > > class := A newAnonymousSubclass > addSlot: (InstanceVariableSlot named: #y); compile: 'm1 > ^100 printString'; yourself. > c := A new becomeForward: class new. > > res := Dictionary new. > col1 := OrderedCollection new. > col2 := OrderedCollection new. > > > 10000 timesRepeat: [ > Smalltalk garbageCollect . > col1 add: [1000000 timesRepeat: [ a m ]] timeToRun]. > > > 10000 timesRepeat: [ > Smalltalk garbageCollect . > col2 add: [1000000 timesRepeat: [ c m ]] timeToRun]. > > > res at: 'a' put: col1. > res at: 'c' put: col2. > res inspect > >

June 20, 2017

Re: [Pharo-users] Finding files in Pharo

by HernÃ¡n Morales Durand

I took the time to review FileSystemDirectoryEntry. UNIX has 3 types of timestamps -The access time is the last time when the content was accessed. -The modification time is last time when the content was modified. -The change time is the last time when the metadata was modified. FileSystemDirectoryEntry>>creationTime This is wrong because there is no such thing as creation time in UNIX. I checked in Linux chmod'ing an empty file and #creationTime displays the chmod "change time". Then added content to the file echo prueba >> test1.txt And both "creation" and "modification" instance variables were updated. I couldn't find #accessTime method to get the last timestamp of last access. Cheers, HernÃ¡n 2017-06-18 10:43 GMT-03:00 Stephane Ducasse <stepharo.self(a)gmail.com>: > I would love that too :). > Can you tell us what is missing from the file properties? > > > > On Sun, Jun 18, 2017 at 4:59 AM, HernÃ¡n Morales Durand > <hernan.morales(a)gmail.com> wrote: > > I would like to find files in Pharo like the UNIX find command: > > > > find . -iname "*.txt" -type f -print > > > > find . \( -iname "*.txt" -o -iname "*.csv" \) -print > > > > find . -maxdepth 2 -name "example*" -type f -print > > > > find . -type f -atime -7 -size +2M -perm 644 -print > > > > Do we have some package on top of FileSystem to make complex find > searches? > > > > HernÃ¡n > > > >

June 20, 2017

Re: [Pharo-users] UUIDGenerator

by phil＠highoctane.be

Spotter rulez :-) On Mon, Jun 19, 2017 at 6:02 PM, Tim Mackinnon <tim(a)testit.works> wrote: > Damnit your rightâ¦. #help keyboard gives you the businessâ¦ nice > > I think the prompt to use Spotter should be in the welcome text though, as > its a bit hidden - maybe is should be in the âExploreâ section. > > Tim > > > On 19 Jun 2017, at 11:30, phil(a)highoctane.be wrote: > > That being said, maybe one can do a spotter extension that looks into the > help topics. > > I did one with windows (should be in Pharo7). > > So one would ho to spotter and put a word followed by #help or #he > > Maybe this is in already! > Phil > > On Mon, Jun 19, 2017 at 10:43 AM, Tim Mackinnon <tim(a)testit.works> wrote: > >> It is in the Pharo help - however I have noticed that Help doesnât have a >> convenient search box and the new Welcome screen that launches with Pharo >> possibly should have a shortcut to useful navigational featuresâ¦. Sounds >> like something I can contributed. >> >> Tim >> >> On 19 Jun 2017, at 00:39, horrido <horrido.hobbies(a)gmail.com> wrote: >> >> I didn't know about the Spotter. That is so frickin' cool!!! >> >> Thanks. >> >> >> philippeback wrote >> >> Spotting for hex is hardly complex. >> >> Shift-Enter hex #im >> >> --> implementors of hex, first one I see is in ByteArray. >> >> Shit-Enter hex #se >> >> --> senders of hex. First one is a test in ByteArray >> >> testHex >> "self debug: #testHex" >> self assert: #[122 43 213 7] hex = '7a2bd507'. >> self assert: #[151 193 242 221 249 32 153 72 179 41 49 154 48 193 99 134] >> hex = '97c1f2ddf9209948b329319a30c16386'. >> self assert: (ByteArray readHexFrom: '7A2BD507') = #[122 43 213 7]. >> self assert: (ByteArray readHexFrom: '7a2bd507') = #[122 43 213 7]. >> >> From this test, one can spot readHexFrom: which uses lowercase or >> uppercase >> for reading. >> >> And asUppercase, Shift-Enter upper, scrolll down as bit, find >> String>>#asUppercase >> >> Spotter is really great at finding stuff, and coupled with tests and >> examples it helps in building understanding. >> >> Agreed, this is not the same as looking for stuff as in, say, Java or >> Python. I find it better in the long run still. >> >> Phil >> >> On Sat, Jun 17, 2017 at 9:23 PM, horrido < >> >> >> horrido.hobbies@ >> >> >> > wrote: >> >> Message 'next' is not understood. >> >> But yes, >> >> UUID new hex asUppercase >> >> works fine. >> >> This is what happens when there is inadequate documentation: you end up >> doing things the *hard* way. >> >> Thanks. >> >> >> >> Sven Van Caekenberghe-2 wrote >> >> Why not just >> >> UUIDGenerator default next hex asUppercase. >> >> Or even >> >> UUID new hex asUppercase. >> >> ? >> >> Since you are using #generateBytes:forVersion: (which is an internal >> method BTW), you must be working in an older Pharo image (older than >> >> 6). >> >> We replaced the UUIDGenerator class, the class comment in from the >> >> newer >> >> version. >> >> On 17 Jun 2017, at 16:27, horrido < >> >> >> horrido.hobbies@ >> >> >> > wrote: >> >> >> Okay, I figured it out. Here's my method: >> >> generateUUID >> | aStream hex s x | >> hex := '0123456789ABCDEF'. >> x := ByteArray new: 16. >> UUIDGenerator default generateBytes: x forVersion: 4. >> s := String new: 32. >> aStream := WriteStream on: s. >> x do: [ :each | aStream nextPut: (hex at: each // 16 + 1). >> aStream nextPut: (hex at: each \\ 16 + 1) ]. >> ^ s >> >> Works like a charm. It would've been nice if a similar example was >> available >> /somewhere/ on the web. >> >> >> >> -- >> View this message in context: >> http://forum.world.st/UUIDGenerator-tp4951725p4951731.html >> Sent from the Pharo Smalltalk Users mailing list archive at >> >> Nabble.com <http://nabble.com/>. >> >> >> >> >> >> >> >> -- >> View this message in context: http://forum.world.st/UUIDGenerator- >> tp4951725p4951743.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com >> <http://nabble.com/>. >> >> >> >> >> >> >> >> >> -- >> View this message in context: http://forum.world.st >> /UUIDGenerator-tp4951725p4951844.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com >> <http://nabble.com/>. >> >> >> > >

June 19, 2017