Thanks John

For the record we are investigating a leak on points.
In pharo 60 we discovered that in certain images I could have 300 000 or more points. :)
Now marcus was analysing the problems with pavel and we had the impression that
some of the points may have been tenured too fast.

Pavel shows that every 5 ms we get a new point.

Stef

On Tue, 31 Jan 2017 05:00:47 +0100, John Brant <brant@refactoryworkers.com> wrote:

I don���t know if there is an existing object reference crawler, but I ported mine from VW. It finds the shortest paths so it is good for finding the reference that is causing the memory leak.
MCHttpRepository
�� �� �� �� location: 'http://www.smalltalkhub.com/mc/JohnBrant/ReferenceFinder/main'
�� �� �� �� user: ''
�� �� �� �� password: ������
Once loaded, you can evaluate something like "ReferenceFinder findPathToInstanceOf: MyClass���.�� That will return a reference path or nil if no path exists from the Smalltalk global to an instance of MyClass. If you want to find a path to a particular instance, you can use ���ReferenceFinder findPathTo: myInst���.

--
Using Opera's mail client: http://www.opera.com/mail/