Re: No reconnect after "Process too big"

On Thu, 2005-05-26 at 10:37 +0200, Nico Kaiser wrote: 
>         Beagle seems to have a "memory leak workaround" which shuts
>         down the process when it's too big. 
> Well, something seems to be shut down, however it's not the process
> that consumes memory. "mono-beagled" still grows constantly from 100
> to about 400 MB (where I have to kill it manually)...

The helper process is restarted as necessary.  The daemon has a failsafe
which kills itself once it gets to some insanely large size (I thought
it was 100 or 200 megs).

Either way, that kind of memory usage is a bug.  It doesn't really
surprise me, though.  We haven't profiled the new message stuff at all


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]