Debugger not closed issue ?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

Debugger not closed issue ?

laurent laffont
Hi,

can you check this please ?

Take an image you work on (not a fresh one), and evaluate:

Debugger closeAllDebuggers.
Smalltalk garbageCollect.
Debugger allInstances size.


On a lot of my images 1 or 2 Debugger instances remains. It's a problem for Autotest, but it also may be a side effect of Autotest, so I want to check.

Cheers,

Laurent Laffont

Pharo Smalltalk Screencasts: http://www.pharocasts.com/
Blog: http://magaloma.blogspot.com/
Reply | Threaded
Open this post in threaded view
|

Re: Debugger not closed issue ?

Sven Van Caekenberghe
Laurent,

I have 4 remaining in a long running 1.1 image.

Sven

On 06 Dec 2010, at 07:57, laurent laffont wrote:

> Hi,
>
> can you check this please ?
>
> Take an image you work on (not a fresh one), and evaluate:
>
> Debugger closeAllDebuggers.
> Smalltalk garbageCollect.
> Debugger allInstances size.
>
>
> On a lot of my images 1 or 2 Debugger instances remains. It's a problem for Autotest, but it also may be a side effect of Autotest, so I want to check.
>
> Cheers,
>
> Laurent Laffont
>
> Pharo Smalltalk Screencasts: http://www.pharocasts.com/
> Blog: http://magaloma.blogspot.com/


Reply | Threaded
Open this post in threaded view
|

Re: Debugger not closed issue ?

laurent laffont
Thanks Sven.

So it's a bug ?

Laurent

On Mon, Dec 6, 2010 at 9:16 AM, Sven Van Caekenberghe <[hidden email]> wrote:
Laurent,

I have 4 remaining in a long running 1.1 image.

Sven

On 06 Dec 2010, at 07:57, laurent laffont wrote:

> Hi,
>
> can you check this please ?
>
> Take an image you work on (not a fresh one), and evaluate:
>
> Debugger closeAllDebuggers.
> Smalltalk garbageCollect.
> Debugger allInstances size.
>
>
> On a lot of my images 1 or 2 Debugger instances remains. It's a problem for Autotest, but it also may be a side effect of Autotest, so I want to check.
>
> Cheers,
>
> Laurent Laffont
>
> Pharo Smalltalk Screencasts: http://www.pharocasts.com/
> Blog: http://magaloma.blogspot.com/



Reply | Threaded
Open this post in threaded view
|

Re: Debugger not closed issue ?

Mariano Martinez Peck
I don't know why nor when, but someone once suggest me to always do 3 timesRepeat: [Smalltalk garbageCollect].

Can you check:

Debugger closeAllDebuggers.
3 timesRepeat: [Smalltalk garbageCollect].
Debugger allInstances size.

If this works, then it would be nice to have someone that explains to us haha



On Mon, Dec 6, 2010 at 9:41 AM, laurent laffont <[hidden email]> wrote:
Thanks Sven.

So it's a bug ?

Laurent


On Mon, Dec 6, 2010 at 9:16 AM, Sven Van Caekenberghe <[hidden email]> wrote:
Laurent,

I have 4 remaining in a long running 1.1 image.

Sven

On 06 Dec 2010, at 07:57, laurent laffont wrote:

> Hi,
>
> can you check this please ?
>
> Take an image you work on (not a fresh one), and evaluate:
>
> Debugger closeAllDebuggers.
> Smalltalk garbageCollect.
> Debugger allInstances size.
>
>
> On a lot of my images 1 or 2 Debugger instances remains. It's a problem for Autotest, but it also may be a side effect of Autotest, so I want to check.
>
> Cheers,
>
> Laurent Laffont
>
> Pharo Smalltalk Screencasts: http://www.pharocasts.com/
> Blog: http://magaloma.blogspot.com/




Reply | Threaded
Open this post in threaded view
|

Re: Debugger not closed issue ?

laurent laffont
Does not change anything... 

Laurent

On Mon, Dec 6, 2010 at 10:26 AM, Mariano Martinez Peck <[hidden email]> wrote:
I don't know why nor when, but someone once suggest me to always do 3 timesRepeat: [Smalltalk garbageCollect].

Can you check:

Debugger closeAllDebuggers.
3 timesRepeat: [Smalltalk garbageCollect].
Debugger allInstances size.

If this works, then it would be nice to have someone that explains to us haha



On Mon, Dec 6, 2010 at 9:41 AM, laurent laffont <[hidden email]> wrote:
Thanks Sven.

So it's a bug ?

Laurent


On Mon, Dec 6, 2010 at 9:16 AM, Sven Van Caekenberghe <[hidden email]> wrote:
Laurent,

I have 4 remaining in a long running 1.1 image.

Sven

On 06 Dec 2010, at 07:57, laurent laffont wrote:

> Hi,
>
> can you check this please ?
>
> Take an image you work on (not a fresh one), and evaluate:
>
> Debugger closeAllDebuggers.
> Smalltalk garbageCollect.
> Debugger allInstances size.
>
>
> On a lot of my images 1 or 2 Debugger instances remains. It's a problem for Autotest, but it also may be a side effect of Autotest, so I want to check.
>
> Cheers,
>
> Laurent Laffont
>
> Pharo Smalltalk Screencasts: http://www.pharocasts.com/
> Blog: http://magaloma.blogspot.com/





Reply | Threaded
Open this post in threaded view
|

Re: Debugger not closed issue ?

Levente Uzonyi-2
In reply to this post by laurent laffont
On Mon, 6 Dec 2010, laurent laffont wrote:

> Hi,
>
> can you check this please ?
>
> Take an image you work on (not a fresh one), and evaluate:
>
> Debugger closeAllDebuggers.
> Smalltalk garbageCollect.
> Debugger allInstances size.
>
>
> On a lot of my images 1 or 2 Debugger instances remains. It's a problem for
> Autotest, but it also may be a side effect of Autotest, so I want to check.

We recently fixed a bug in OCompletion (load OCompletion-klub.84 for the
fix), that resulted in hanging debugger instances. To reproduce the issue:
- open a debugger
- type something to the inspector in the lower right panel and make sure
you've triggered OCompletion.
After closing the debugger it won't be garbage collected.


Levente

>
> Cheers,
>
> Laurent Laffont
>
> Pharo Smalltalk Screencasts: http://www.pharocasts.com/
> Blog: http://magaloma.blogspot.com/
>

Reply | Threaded
Open this post in threaded view
|

Re: Debugger not closed issue ?

cedreek
In reply to this post by laurent laffont
I have 6 of them :(

By chasing pointers, it seems to be related to ObjectExplorerWrapper... 

hth,

Cédrick




On Mon, Dec 6, 2010 at 9:41 AM, laurent laffont <[hidden email]> wrote:
Thanks Sven.

So it's a bug ?

Laurent


On Mon, Dec 6, 2010 at 9:16 AM, Sven Van Caekenberghe <[hidden email]> wrote:
Laurent,

I have 4 remaining in a long running 1.1 image.

Sven

On 06 Dec 2010, at 07:57, laurent laffont wrote:

> Hi,
>
> can you check this please ?
>
> Take an image you work on (not a fresh one), and evaluate:
>
> Debugger closeAllDebuggers.
> Smalltalk garbageCollect.
> Debugger allInstances size.
>
>
> On a lot of my images 1 or 2 Debugger instances remains. It's a problem for Autotest, but it also may be a side effect of Autotest, so I want to check.
>
> Cheers,
>
> Laurent Laffont
>
> Pharo Smalltalk Screencasts: http://www.pharocasts.com/
> Blog: http://magaloma.blogspot.com/






Reply | Threaded
Open this post in threaded view
|

Re: Debugger not closed issue ?

laurent laffont
In reply to this post by Levente Uzonyi-2

We recently fixed a bug in OCompletion (load OCompletion-klub.84 for the fix), that resulted in hanging debugger instances. To reproduce the issue:
- open a debugger
- type something to the inspector in the lower right panel and make sure you've triggered OCompletion.
After closing the debugger it won't be garbage collected.


Thank you Levente. How can I check that my immortal debuggers are the consequence of this bug ?

Laurent.

 


Levente



Cheers,

Laurent Laffont

Pharo Smalltalk Screencasts: http://www.pharocasts.com/
Blog: http://magaloma.blogspot.com/



Reply | Threaded
Open this post in threaded view
|

Re: Debugger not closed issue ?

Levente Uzonyi-2
On Mon, 6 Dec 2010, laurent laffont wrote:

>>
>>
>> We recently fixed a bug in OCompletion (load OCompletion-klub.84 for the
>> fix), that resulted in hanging debugger instances. To reproduce the issue:
>> - open a debugger
>> - type something to the inspector in the lower right panel and make sure
>> you've triggered OCompletion.
>> After closing the debugger it won't be garbage collected.
>>
>
>
> Thank you Levente. How can I check that my immortal debuggers are the
> consequence of this bug ?

If there are more than one instances (or sub-instances) of ECController in
your image after closing all windows, then it's very probable that this is
the cause of the problem.

If you load OCompletion-klub.84 (which is the last version of OCompletion
that's compatible with Pharo 1.1) and evaluate this:

ECController allSubInstancesDo: [ :each | each editor ].
Smalltalk garbageCollect.

Then the debuggers should be gone.


Levente

>
> Laurent.
>
>
>
>>
>>
>> Levente
>>
>>
>>
>>> Cheers,
>>>
>>> Laurent Laffont
>>>
>>> Pharo Smalltalk Screencasts: http://www.pharocasts.com/
>>> Blog: http://magaloma.blogspot.com/
>>>
>>>
>>
>

Reply | Threaded
Open this post in threaded view
|

Re: Debugger not closed issue ?

Schwab,Wilhelm K
In reply to this post by Mariano Martinez Peck
Just out of curiosity, I went directly to

   Debugger allInstances size

and got zero :)  This is in a far from fresh 1.1.1 image.  I do not use eCompletion or AutoTest.

Bill


________________________________________
From: [hidden email] [[hidden email]] On Behalf Of Mariano Martinez Peck [[hidden email]]
Sent: Monday, December 06, 2010 4:26 AM
To: [hidden email]
Subject: Re: [Pharo-project] Debugger not closed issue ?

I don't know why nor when, but someone once suggest me to always do 3 timesRepeat: [Smalltalk garbageCollect].

Can you check:

Debugger closeAllDebuggers.
3 timesRepeat: [Smalltalk garbageCollect].
Debugger allInstances size.

If this works, then it would be nice to have someone that explains to us haha






Reply | Threaded
Open this post in threaded view
|

Re: Debugger not closed issue ?

laurent laffont
In reply to this post by Levente Uzonyi-2

On Mon, Dec 6, 2010 at 2:02 PM, Levente Uzonyi <[hidden email]> wrote:
On Mon, 6 Dec 2010, laurent laffont wrote:



We recently fixed a bug in OCompletion (load OCompletion-klub.84 for the
fix), that resulted in hanging debugger instances. To reproduce the issue:
- open a debugger
- type something to the inspector in the lower right panel and make sure
you've triggered OCompletion.
After closing the debugger it won't be garbage collected.



Thank you Levente. How can I check that my immortal debuggers are the
consequence of this bug ?

If there are more than one instances (or sub-instances) of ECController in your image after closing all windows, then it's very probable that this is the cause of the problem.

I have no instance.

 

If you load OCompletion-klub.84 (which is the last version of OCompletion that's compatible with Pharo 1.1) and evaluate this:

ECController allSubInstancesDo: [ :each | each editor ].
Smalltalk garbageCollect.

Then the debuggers should be gone.

I've tried but they are still here. So it's another issue (maybe Autotest. I will work without Autotest to see if I can reproduce the problem).


Laurent.
 


Levente



Laurent.





Levente



Cheers,

Laurent Laffont

Pharo Smalltalk Screencasts: http://www.pharocasts.com/
Blog: http://magaloma.blogspot.com/