> On 22. Jul 2017, at 20:40, Pavel Krivanek <pavel.kriva...@gmail.com> wrote: > > In the most of standard cases you can use ReferenceFinder. It is in the > catalog too and I think that we should integrate it into the Pharo because it > is extremely useful for the memory leaks detection. It does not require > snapshots and I firstly try it before applying of the RefsHunter (and I say > that as the author of the RefsHunter ;-))
Cool and thank you for RefsHunter! I found RefsHunter by typing "leak". Could we get this attached to the ReferenceFinder in the catalog as well? holger
