Re: [Pharo-dev] Memory leaks

The catalog is updated once per day or so... -- Pavel 2017-02-01 16:01 GMT+01:00 Alexandre Bergel : > I cannot find ReferenceFinder in the catalog. > Any idea? > > Alexandre > > > > On Jan 31, 2017, at 8:17 PM, Torsten Bergmann wrote: > > > > I created

Re: [Pharo-dev] Memory leaks

I cannot find ReferenceFinder in the catalog. Any idea? Alexandre > On Jan 31, 2017, at 8:17 PM, Torsten Bergmann wrote: > > I created a config (in original repo and MetaRepoForPharo60) so it should be > available > In the morning in catalog already. > > Thanks to John for

Re: [Pharo-dev] Memory leaks

On 01/31/2017 06:45 AM, stepharong wrote: thierry we have pointersTo and I imagine that it is not good enough. Do you confirm? #pointersTo appears to be the same as #allReferences and #allOwners in other Smalltalk implementations. These methods are terrible for finding the reason for the

Re: [Pharo-dev] Memory leaks

On 01/31/2017 04:02 AM, Pavel Krivanek wrote: Very nice tool. I think it cannot find objects pointed only by a stack of some processes so it may be handy to put them to the global space. Smalltalk globals at: #Stacks put: ((Process allInstances collect: [:p | (p suspendedContext) ifNotNil:

Re: [Pharo-dev] Memory leaks

2017-01-31 13:42 GMT+01:00 stepharong : > 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

Re: [Pharo-dev] Memory leaks

thierry we have pointersTo and I imagine that it is not good enough. Do you confirm? Stef On Tue, 31 Jan 2017 10:00:39 +0100, Thierry Goubier wrote: Hi John, thanks for that tool. Have found a leak that I have been chasing like forever... I would vote to

Re: [Pharo-dev] Memory leaks

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.

Re: [Pharo-dev] Memory leaks

Very nice tool. I think it cannot find objects pointed only by a stack of some processes so it may be handy to put them to the global space. Smalltalk globals at: #Stacks put: ((Process allInstances collect: [:p | (p suspendedContext) ifNotNil: #stack ]) reject: #isNil) asOrderedCollection.

Re: [Pharo-dev] Memory leaks

Hi John, thanks for that tool. Have found a leak that I have been chasing like forever... I would vote to integrate that into the base image. Regards, Thierry 2017-01-31 5:00 GMT+01:00 John Brant : > > On Jan 30, 2017, at 3:57 PM, Alexandre Bergel

Re: [Pharo-dev] Memory leaks

> On Jan 30, 2017, at 3:57 PM, Alexandre Bergel wrote: > > > The problem is still present. > Looking at the pointers > > There was an object reference crawler no? I remember someone worked on this? > I tried sending #pointersTo but I without much success on

Re: [Pharo-dev] Memory leaks

> On 30 Jan 2017, at 22:57, Alexandre Bergel wrote: > > Hi! > > It looks like that we are currently suffering memory leaks. That is a bit strong a statement. Maybe some IDE UI stuff might sometimes hold onto something too long. > In march 2015 it was said in the

[Pharo-dev] Memory leaks

Hi! It looks like that we are currently suffering memory leaks. In march 2015 it was said in the mailing list: -=-=-=-=-=-=-=-= I also tried this: 1. Create a dummy class: Object subclass: #AAA instanceVariableNames: 'x' classVariableNames: '' category: 'AAA'.

[Pharo-dev] Memory Leaks (may be due to rubric)

Message transféré Sujet : [Moose-dev] Re: build ? Date : Thu, 9 Jul 2015 15:22:23 +0200 De :Andrei Chis chisvasileand...@gmail.com Répondre à :Moose-related development moose-...@iam.unibe.ch Pour : Moose-related development moose-...@iam.unibe.ch I added

Re: [Pharo-dev] Memory leaks with Spec?

://pharo.fogbugz.com/f/cases/10787/Make-Announcements-Weak-By-Default Blocked on Issue 4312: Ephemerons integration - Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-dev-Memory-leaks-with-Spec-tp4689839p4690513.html Sent from the Pharo Smalltalk Developers mailing list

Re: [Pharo-dev] Memory leaks with Spec?

Le 25/05/2013 13:59, Benjamin a écrit : I am pretty sure to only use weak registration (why aren't all the registration weak btw ??) It may be a problem somewhere else :( I hit that problem a while ago. I couldn't find where it was holding the instances, even with the help of the strong

Re: [Pharo-dev] Memory leaks with Spec?

2013/5/27 stephane ducasse stephane.duca...@free.fr we found the problem. It is not spec but the EyeInspector polling update. So we should find a solution. Probably it should register WindowClosed and kill the process. Actually the inspector is already registered on WindowClosed event. This

[Pharo-dev] Memory leaks with Spec?

Hi guys this is strange I cannot get rid of Spec based ui instances. I tried many LoggerUI allInstances do: [ :each | SystemAnnouncer uniqueInstance unsubscribe: each ] LoggerUI allInstances do: #delete. Smalltalk garbageCollect Nothing changes. Each time I create and close it does

Re: [Pharo-dev] Memory leaks with Spec?

I am pretty sure to only use weak registration (why aren't all the registration weak btw ??) It may be a problem somewhere else :( Ben On May 25, 2013, at 1:55 PM, Igor Stasenko siguc...@gmail.com wrote: On 25 May 2013 13:49, Stéphane Ducasse stephane.duca...@inria.fr wrote: Hi guys this

Re: [Pharo-dev] Memory leaks with Spec?

On 25 May 2013 14:01, stephane ducasse stephane.duca...@free.fr wrote: Igor I will use weak (may be weak should be default and we should propose strong as an option) but I do not understand since LoggerUI allInstances do: [ :each | SystemAnnouncer uniqueInstance unsubscribe: each ]

Re: [Pharo-dev] Memory leaks with Spec?

maybe have announcer on:... which gives you weak subscriptions and announcer strong on:... following Make common things easy, rare things possible - Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-dev-Memory-leaks-with-Spec-tp4689839p4689852.html Sent from the Pharo

Re: [Pharo-dev] Memory leaks with Spec?

Sean P. DeNigris wrote Yes!!! From http://forum.world.st/Unsubscribing-for-Announcements-tp3220751p4083086.html : But IIRC ephemerons are needed for subscribing blocks that way... - Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-dev-Memory-leaks-with-Spec