I took a look, and that bug seems to be indicated for hot reloads. Would it apply here?
-Mike On 3/21/06, Mike Snare <[EMAIL PROTECTED]> wrote: > 4.0, 1.1. > > Was the memory leak in relation to this? The only major fix I was > aware of for 1.1.1 was the performance issue for threaded services. > > -Mike > > On 3/21/06, James Carman <[EMAIL PROTECTED]> wrote: > > What version of Tapestry are you using? If it's 4.0, what version of > > HiveMind are you using? There was a known memory leak in 1.1 which was > > fixed in 1.1.1. > > > > -----Original Message----- > > From: Mike Snare [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, March 21, 2006 1:30 PM > > To: Tapestry users > > Subject: Memory leak? > > > > I'm pretty sure there's a memory leak in tapestry because the memory > > usage climbs and climbs when caching is disabled. > > > > I understand that in a production environment you probably wouldn't > > want caching disabled, but it seems tapestry should throw out whatever > > it's creating if it's not going to use them. I don't think this is > > happening. > > > > -Mike > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
