On 30 Jan 2017, at 22:57, Alexandre Bergel alexandre.bergel@me.com 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 mailing list:

-=-=-=-=-=-=-=-= I also tried this:

1. Create a dummy class:

Object subclass: #AAA instanceVariableNames: 'x' classVariableNames: '' category: 'AAA'.

2. Open a Playground and do it and go on this:

a := #AAA asClass new.

And why would you do that ?

You assign to a workspace variable, hence your object is held in the scope of the Playground.

So whenever the Playground gets retained by some other object, like an announcement, event or whatever, your object get retained too.

I am 100% sure that if you do

1e6 timesRepeat: [ #AAA asClass new ]. 3 timesRepeat: [ Smalltalk garbageCollect ]. #AAA asClass allInstances isEmpty.

=> true

3. In the second pane go on "self"

4. Close the Playground

5. Execute:

3 timesRepeat: [ Smalltalk garbageCollect ].

6. Check:

#AAA asClass allInstances.

7. Repeat if necessary, and after a while, the result after step 6 is not empty.

-=-=-=-=-=-=-=-=

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 identifying the cause of this leak.

Any idea?

Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Last week I was hunting the memory leaks with RefsHunter because the abnormal amount of Point instances in the object memory.

FreeTypeCache cleanUp. Clipboard startUp: true. RubEditingState allInstances do: [ :each | each instVarNamed: #undoManager put:nil]. GTPlayBook reset. EditorFindReplaceDialogWindow cleanUp. ActiveHand resetClickState; releaseAllFocus. UITheme current focusIndicator: nil. 40 timesRepeat: [ 1 second wait. World doOneCycle. ].

I will try to find the reason why they appear, not only how to kill them.

Cheers, -- Pavel

2017-01-30 22:57 GMT+01:00 Alexandre Bergel alexandre.bergel@me.com:

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'.

2. Open a Playground and do it and go on this:

a := #AAA asClass new.

3. In the second pane go on "self"

4. Close the Playground

5. Execute:

3 timesRepeat: [ Smalltalk garbageCollect ].

6. Check:

#AAA asClass allInstances.

7. Repeat if necessary, and after a while, the result after step 6 is not

empty.

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 identifying the cause of this leak.

Any idea?

Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

---

Moose-dev mailing list Moose-dev@list.inf.unibe.ch https://www.list.inf.unibe.ch/listinfo/moose-dev