[Seaside] Memory leak, any tips?

Lukas Renggli renggli at gmail.com
Wed Jun 3 11:03:32 UTC 2009


Yeah, usually that usually works.

In your case it could be that data still hangs around WAKom or within
the process list.

Make sure that you kill all Seaside processes and restart the server.

Lukas

On Wed, Jun 3, 2009 at 12:59 PM, John McKeon <p3anoman at gmail.com> wrote:
> WARegistry clearAllHandlers
> Smalltalk garbageCollect
>
> Works for me every time :)
>
> John
>
> 2009/6/3 Hilaire Fernandes <hilaire at ofset.org>
>>
>> With Seaside 2.8.
>>
>> I accidently wrote:
>>
>> html div: (super renderTerm: term on: html)
>>
>> in place of
>>
>> html div: [super renderTerm: term on: html])
>>
>> It caused an infinite recursion, I have to kill the seaside process to
>> recover, but now my image has grown to 100MB.
>> Not sure it is related, but I see about 50 WASession hanging around,
>> even when I shut down.
>>
>> With
>> WARegistry clearAllHandlers.
>> Smalltalk garbageCollect.
>>
>> the WASession are still there.
>>
>>
>> Strangely I also have many component hanging in memory.
>>
>> Any tips? I am not sure were to look to chasse pointers.
>>
>> Hilaire
>>
>>
>> _______________________________________________
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>>
>
>
>
> --
> http://jmck.seasidehosting.st
>
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>
>



-- 
Lukas Renggli
http://www.lukas-renggli.ch


More information about the seaside mailing list