[Celerity-users] memory leaks and serialize blockage

[Tomasz Kalkosiński]

On Wednesday 09 of December 2009 23:58:14 jason franklin-stokes wrote:
> 
> the method enable_event_listener has 2 side effects. 
> 
> 1. it seems to hold on to objects which result in the javascript threads not being able to close. so over time memory useage grows and cannot be collected by the GC
> 
> 2. as soon as enable_event_listener has been called it becomes no longer possible to serilaize webclient. 
> 
> question. 
> 
> what exactly is this method for? is there another way of doing this so that it does hold objects in memory and does not get in the way of serialize?
> 
> would be great to get some feedback

Hello jason

I use Celerity with spawned 10 threads and I saw memory consuming is really high in here too.

Can you provide some tests for your assumptions about enable_event_listener? I don't know the real purpose of this method.

Greetings,
Tomasz Kalkosiński

> 
> thanks
> 
> jason.
> 
> _______________________________________________
> Celerity-users mailing list
> Celerity-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/celerity-users
>