Sounds like I fixed one bug to introduce another...

I'll see if I can set up a memory leak test to run overnight in the next few
days.

Mark

On Wed, Jul 8, 2009 at 2:36 PM, Elliott Sprehn <espr...@gmail.com> wrote:

>
>
> On Jul 7, 1:27 pm, Brian G <brian-goo...@vfive.com> wrote:
> > On Jul 1, 10:40 pm, Elliott Sprehn <espr...@gmail.com> wrote:
> >
> > > I updated to the Trunk version and the errors have seemed to go away.
> > > I'm going to load test it and low mem test it later this week and see
> > > if it holds up.
> >
> > I'm interested in your findings - I'm reasonably sure there is a mem
> > leak issue in the trunk version of Transfer.  The issue I've been
> > struggling with on another mailing list look like they are Transfer
> > related.  I've rolled back to 1.1 and my unit test shows no leaky
> > objects.  Mark has a heap of mine to look at so I'm sure we'll get
> > confirmation one way or the other... my box was running out of heap in
> > as little as 24 hours so keep an eye on it.
>
> Thanks, I'll keep an eye on that. We did run out of memory a few days
> ago with a "Java heap space null" error, and then just a day or so ago
> the server got super sluggish. I forced a full restart of our platform
> (restarts every CF app, transfer, coldspring, etc.) and it freed about
> 250mb of RAM and everything was normal again.
>
> I'm watching to see if this happens again.
>
> -Elliott
> >
>


-- 
E: mark.man...@gmail.com
T: http://www.twitter.com/neurotic
W: www.compoundtheory.com

--~--~---------~--~----~------------~-------~--~----~
Before posting questions to the group please read:
http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer

You received this message because you are subscribed to the Google Groups 
"transfer-dev" group.
To post to this group, send email to transfer-dev@googlegroups.com
To unsubscribe from this group, send email to 
transfer-dev-unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/transfer-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to