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

Points, Free type fonts cache and memory leaks

by Pavel Krivanek

Hi, It is very common to see in actively used images that the number of instances of Point is very high. Sometimes in order of hundreds of thousands. There is several reasons for that: Pharo every few milliseconds checks for the new display size. That check generates two instances of Point that are not garbage collected in reasonably short time. So if you periodically check the result of "Point allInstances size", you will see that it is quickly growing. On the other hand. That Point instances are not referenced by anyone so as soon as you do Smalltalk garbageCollect, the amount of Points in reduced. And they are correctly garbage collected by the VM after some time which is often longer than one minute. So no action needed. Then a lot of Points is stored in FreeTypeCache. That cache is a huge beast and it tries to store a small form for every new rendered character glyph. That means for every font, every pixel size etc. It sounds reasonable but the main reason why the cache can be very huge is in the fact that it stores a new glyph for every sub-pixel variant too! Every FreeTypeChacheEntry also contains several Point instances so it is a important source of them. Fortunately, this cache has mechanisms to limit its size. This limit now set to expected size of 5MB, see FreeTypeChache>>#defaultMaximumSize. So in the end, probably no immediate fix is needed although this cache deserves revision. And then we have a Text related memory leak that I will try to investigate. This memory leak does not let to garbage collect any tool window as soon as clipboard or history (undo) was used in it. Cheers, -- Pavel

Feb. 14, 2017

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60389 Home: https://github.com/pharo-project/pharo-core

Feb. 14, 2017

[pharo-project/pharo-core] b057bb: 60389

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: b057bb3e23b9828a8f0b1373c650e209254dee3a https://github.com/pharo-project/pharo-core/commit/b057bb3e23b9828a8f0b1373… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-02-14 (Tue, 14 Feb 2017) Changed paths: A Reflectivity-Tools.package/Watchpoint.class/instance/printing/printLastValue.st M Reflectivity-Tools.package/Watchpoint.class/instance/printing/printOn_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60388.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60389.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60388.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60389.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M SmartSuggestions.package/SugsWatchpointSuggestion.class/instance/execution/execute.st M Tests.package/SourceFileArrayTest.class/instance/testing/testProtocol.st M Tests.package/SourceFileArrayTest.class/instance/testing/testTimeStamp.st Log Message: ----------- 60389 19701 Watchpoint should not ask for name https://pharo.fogbugz.com/f/cases/19701 19700 testTimeStamp should not use hardcoded timestamp https://pharo.fogbugz.com/f/cases/19700 19699 testProtocol should not test timestamp https://pharo.fogbugz.com/f/cases/19699 http://files.pharo.org/image/60/60389.zip

Feb. 14, 2017

Re: [Pharo-dev] IPv6 support [VM]

by Esteban Lorenzano

there was some work but it was not finished, then is kind of aborted (for now). if you want to take a look there are some primitives in the networking pluginâ¦ never finished, never tested, never done :) Esteban > On 14 Feb 2017, at 13:20, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > Hi, > > does anyone know what is the state of Pharo's IPv6 support? > > I've found some discussion from 2009/2010 talking about it and making changes to the VM, but it seems incomplete. > > Creating IPv6 socket seems to be supported on the VM side (and I had no failure when I modified the netType from 0 to 3 in Socket>>initialize:) > > https://github.com/pharo-project/pharo-vm/blob/master/opensmalltalk-vm/plat… > https://github.com/pharo-project/pharo-vm/blob/master/opensmalltalk-vm/plat… > > However creating connection fails I guess here > https://github.com/pharo-project/pharo-vm/blob/master/opensmalltalk-vm/src/… > > And even if it didn't fail there, sqSocketConnectToPort accepts address in sqInt (4 bytes), and sets the type to AF_INET > https://github.com/pharo-project/pharo-vm/blob/master/opensmalltalk-vm/plat… > > Was the effort abandoned? Am I doing something wrong and it actually should work? > > > Also NetNameResolver in Pharo is IPv4 only, but that's not an issue here. > > Thanks, > Peter >

Feb. 14, 2017

IPv6 support [VM]

by Peter Uhnak

Hi, does anyone know what is the state of Pharo's IPv6 support? I've found some discussion from 2009/2010 talking about it and making changes to the VM, but it seems incomplete. Creating IPv6 socket seems to be supported on the VM side (and I had no failure when I modified the netType from 0 to 3 in Socket>>initialize:) https://github.com/pharo-project/pharo-vm/blob/master/opensmalltalk-vm/plat… https://github.com/pharo-project/pharo-vm/blob/master/opensmalltalk-vm/plat… However creating connection fails I guess here https://github.com/pharo-project/pharo-vm/blob/master/opensmalltalk-vm/src/… And even if it didn't fail there, sqSocketConnectToPort accepts address in sqInt (4 bytes), and sets the type to AF_INET https://github.com/pharo-project/pharo-vm/blob/master/opensmalltalk-vm/plat… Was the effort abandoned? Am I doing something wrong and it actually should work? Also NetNameResolver in Pharo is IPv4 only, but that's not an issue here. Thanks, Peter

Feb. 14, 2017

Re: [Pharo-dev] Slack, fragmentation and design information

by Dimitris Chloupis

The thing that annoy me the most with C2 is that almost each time I googled Smalltalk when I wasstill a beginner with Pharo and Smalltalk this came up often http://wiki.c2.com/?WhyIsSmalltalkDead But yes I agree, its nice to have a place to put information and never worry about it getting delete. On the matter of Slack, my Discord bot , lighthouse has evolved to message the online chat with replies to the mailing list which gave a good look inside how chat bots work. Esteban made me admin in Slack so the next step is to have the bot connect to Slack and copy the Slack messages to Discord chat , which means you wont need a Slack plan, because Discord never deletes messages. This way we can use Discord as a backup for our Slack messages and the bot could also copy the messages to a file , I am considering SQLite which we support, so that we never lose the content. Problem solved and it also solves the problem of fragmentation. The mailing list is already connected to Discord via my bot, Slack will also connect to discord via my bot and pretty much anything else can be brought into this hub so everyone can keep using Slack or whatever way he or she prefers to communicate without the fear of fragmentation. On Tue, Feb 14, 2017 at 1:07 PM Pierce Ng <pierce(a)samadhiweb.com> wrote: > On Mon, Feb 13, 2017 at 11:51:23PM +0000, Dimitris Chloupis wrote: > > wiki. They end messy and very badly documented. Especially c2 is quite a > > mess, probably the worst wiki I have ever seen. > > To me the lack of organization is in the nature of a wiki. It's like a > place to > be explored. Must be said C2's Smalltalk content is rather meh last I > looked a > few years ago. > > <obPharoContent> My personal wiki has ~800 pages. Already there are nooks > and > crannies that I've not visited in a while. Naturally, Pharo is the tool I > am > using to help me navigate. > > Pierce > >

Feb. 14, 2017

Re: [Pharo-dev] Slack, fragmentation and design information

by Pierce Ng

On Mon, Feb 13, 2017 at 11:51:23PM +0000, Dimitris Chloupis wrote: > wiki. They end messy and very badly documented. Especially c2 is quite a > mess, probably the worst wiki I have ever seen. To me the lack of organization is in the nature of a wiki. It's like a place to be explored. Must be said C2's Smalltalk content is rather meh last I looked a few years ago. <obPharoContent> My personal wiki has ~800 pages. Already there are nooks and crannies that I've not visited in a while. Naturally, Pharo is the tool I am using to help me navigate. Pierce

Feb. 14, 2017

Re: [Pharo-dev] [QA] Scoped

by Ben Coman

Maybe... Browse selected package in a context that limits the scope of analysis tools (e.g. 'Senders of...', 'Implementors of...', 'Class refs...') cheers -ben On Tue, Feb 14, 2017 at 5:26 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > Hi, > > What about the Nautilus Scoped button tooltip to be more explicit for > newbie? > > What about: > > 'Browse the selected packaged in a scoped context: analysis tools as > 'Senders of...', 'Implementors of...', 'Class refs...', etc. are limited > to the package. > > Thanks > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > > >

Feb. 14, 2017

[QA] Scoped

by Hilaire

Hi, What about the Nautilus Scoped button tooltip to be more explicit for newbie? What about: 'Browse the selected packaged in a scoped context: analysis tools as 'Senders of...', 'Implementors of...', 'Class refs...', etc. are limited to the package. Thanks Hilaire -- Dr. Geo http://drgeo.eu

Feb. 14, 2017

Re: [Pharo-dev] GLMAction and PharoShortcut

by Hilaire

Thanks for the update. Based on previous Steph post, should we move this bug ticket to Pharo7 or keep it for Pharo6? Hilaire Le 13/02/2017 Ã 18:46, Andrei Chis a Ã©crit : > Hi, > > Good catch. Indeed GLMAction>>#shortcutAsString should go to the keymap object. > > Apart from the inconsistencies that you mention, there is in my view > another one. For example, in the debugger in the context menu of the > stack modifiers are displayed using special characters (at least on > mac). In tooltips they are display using Shift, Meta, Ctrl, etc. > Right now the logic for printing shortcuts that way is in > ToggleMenuItemShortcut>>#owner:keyText: and it's a bit complicated to > reuse. See GTSpotterCategoryTitleBrick>>#setShortcutBrickTextFor: for > an example. > > Cheers, > Andrei -- Dr. Geo http://drgeo.eu

Feb. 14, 2017