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

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

by phil＠highoctane.be

On Mon, Jun 19, 2017 at 11:52 AM, Davide Varvello via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > > > ---------- Forwarded message ---------- > From: Davide Varvello <varvello(a)yahoo.com> > To: pharo-users(a)lists.pharo.org > Cc: > Bcc: > Date: Mon, 19 Jun 2017 02:52:08 -0700 (PDT) > Subject: Re: Bloated image again. Memory leak? > Thank you very much Phil, > Your code works! The image went from 600MB to 80MB > I suffered from such a thing for a long time, and thanks to ClÃ©ment and Pavel, we are not having to suffer that bloat anymore :-) This article is worth a read for making things fast(er) in some cases (if you got to 600MB then you were inspecting decently sized collections): https://clementbera.wordpress.com/2017/03/12/tuning-the-pharo-garbage-colle… Phil > 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. > > 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 19, 2017

Re: [Pharo-users] UUIDGenerator

by phil＠highoctane.be

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. > > > > > > > > -- > View this message in context: http://forum.world.st/UUIDGenerator- > tp4951725p4951743.html > Sent from the Pharo Smalltalk Users mailing list archive at 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

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

by Esteban Lorenzano

> 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 <mailto:varvello@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 <mailto:pharo-users@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 <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 <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 <http://forum.world.st/Bloated-image-again-Memory-leak-tp4951862p4951885.html> > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com <http://nabble.com/>.

June 19, 2017

Re: Bloated image again. Memory leak?

by Davide Varvello

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. 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 19, 2017

Re: [Pharo-users] UUIDGenerator

by Tim Mackinnon

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. >>>>> >>> >>> >>> >>> >>> >>> -- >>> View this message in context: http://forum.world.st/UUIDGenerator- >>> tp4951725p4951743.html >>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >>> >>> >>> > > > > > > -- > View this message in context: http://forum.world.st/UUIDGenerator-tp4951725p4951844.html <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

Re: [Pharo-users] Finding files in Pharo

by Alistair Grant

Hi Hernan, On Sat, Jun 17, 2017 at 11:59:59PM -0300, Hern??n Morales Durand 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? You might also like to look at the FileSystemVisitor class and subclasses. Currently you can't strictly do a "-type f" test. The closest at the moment is "isDirectory" and "isDirectory not" (which is what #isFile is defined as). I've got some patches lined up which will allow you to test things like #isRegular (which matches "-type f"), #isSymlink, etc. But it will be a while before they become available as it involves a new VM plugin. Cheers, Alistair

June 19, 2017

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

by phil＠highoctane.be

Check https://gist.github.com/philippeback/39c63bb5aa26b79098511cdfea4fea7e Phil On Mon, Jun 19, 2017 at 8:45 AM, Davide Varvello via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > > > ---------- Forwarded message ---------- > From: Davide Varvello <varvello(a)yahoo.com> > To: pharo-users(a)lists.pharo.org > 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. > > > >

June 19, 2017

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

by Nicolai Hess

Done: 20166 <https://pharo.fogbugz.com/f/cases/20166/wrong-cliprect-on-transformed-athen…> 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 19, 2017

Bloated image again. Memory leak?

by Davide Varvello

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.

June 19, 2017

Re: [Pharo-users] Teapot session

by Sven Van Caekenberghe

If you are talking about ZnServerSessions, the ones returned from ZnRequest>>#session, then the answer is that they are eligible for expiration and cleanup after 1 hour (see ZnServerSession>>#isValid). Cleanup happens inZnSingleThreadedServer>>#periodTasks. Right now, the expiration time is a fixed constant. > On 19 Jun 2017, at 08:08, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Teapot is a layer on zinc so you may check the Zinc chapters (I do not > know if this is there). > > > On Mon, Jun 19, 2017 at 1:42 AM, horrido <horrido.hobbies(a)gmail.com> wrote: >> Does Teapot's (ZnRequest's?) session ever expire? What is the expiry period? >> >> I can't find where it's specified or configured. >> >> >> >> >> -- >> View this message in context: http://forum.world.st/Teapot-session-tp4951845.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >

June 19, 2017