Re: summary of current memory leak problem

2003-12-12 Thread John Casey
Wow, that's great! I can't wait to take it for a spin. john On Fri, 2003-12-12 at 19:17, [EMAIL PROTECTED] wrote: > It is fixed in the 1.0 branch. > > The branch still has a few more issues to be resolved, but it's looking > good. > -- > dIon Gillard, Multitask Consulting > Blog: http://bl

Re: summary of current memory leak problem

2003-12-12 Thread dion
It is fixed in the 1.0 branch. The branch still has a few more issues to be resolved, but it's looking good. -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ John Casey <[EMAIL PROTECTED]> wrote on 13/12/2003 09:39:06 AM: > I have scanned the bugs listed

Re: summary of current memory leak problem

2003-12-12 Thread John Casey
BTW, I have been able to deduce from my own usage patterns that most of the leak seems to take place in the jelly ant task wrapper tag...for whatever it's worth, this is always where the memory disappears never to reappear again... -j On Fri, 2003-12-12 at 17:39, John Casey wrote: > I have scanne

summary of current memory leak problem

2003-12-12 Thread John Casey
I have scanned the bugs listed in jira, looking for the memory leak I'm experiencing when I run a reactor-ized multiproject:xxx build. What I find are several bugs which talk about various memory leaks, and are marked fixed (most in the relatively distant past), and some more which describe the "