On Tue, Feb 14, 2017 at 9:54 PM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:
> 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.

Even though these get cleared out, its still extra work for the GC.�� Presumably most of the time the display size is identical to the last one, so I wonder if the existing screen size might be passed to the primitive to test and avoid creating a new new point if its the same.�� Off the top of my head, something like this (untested)... ��

�� DisplayScreen class >> isActualScreenSizeX: width Y: height
�� �� �� <primitive: 106>