[Seaside] Lurking SessionObjects

[Julian Fitzell]

Hey Derek,

instances of subclasses of WASessionObject are snapshotted on every page 
view so you can roll their state back when the user uses the back 
button, etc.  My guess is that your cache objects are holding on to 
these objects.

As for getting rid of them, you could iterate over the keys in the cache 
and remove each one.  Or you could presumably delete the application 
definition and create a new one so that a new cache is created (I'm only 
guessing at this, haven't tried it to make sure).  Then a GC should free 
them up.

Give another shout if this doesn't work for you.  I could dig deeper and 
see if there's some other reason they're being held around.  But if you 
haven't tried any of the above, then I would guess the cache is the culprit.

Derek Brans wrote:

> Avi or Julian:
> I have many sub-instances of WASessionObject in my image.  Why do they
> hang around and how can I get rid of them?
>
> Thanks,
> Derek
>
> Nerd on a Wire: Web and Information Solutions
> Website Design - Database Systems - Site Hosting
> 604.874.6463
> mailto:info@nerdonawire.com
> For more information, visit http://nerdonawire.com
>
> _______________________________________________
> Seaside mailing list
> Seaside@lists.squeakfoundation.org
> http://lists.squeakfoundation.org/listinfo/seaside



-- 
julian@beta4.com
Beta4 Productions (http://www.beta4.com)