Anectodal evidence is that there isn't a memory leak problem. Tapestry does do a bit of object pooling, but includes a janitor thread to eventually delete unused objects in the pools. Dorothy G. posted some performance results recently that also included observations of memory usage.
I haven't done any hard core memory analysis in over a year (I no longer have access to the tools ... they were owned by a prior employer). A few specific classes, such as PropertyHelper, keep local caches of objects in static variables. By far and large, however, static variables are not used in Tapestry ... partly because of the desirablility of pluggable components and to support the ability to flush out the cache of pools and specifications and such (the reset service). In other words, careful memory management is crafted into Tapestry. The framework reflects careful thought about the lifecycle of created objects, ensuring that they will, eventually, be removed when no longer needed. Please do some analysis and report back your results. -- [EMAIL PROTECTED] http://tapestry.sf.net > Has anyone profiled a tapestry application for memory dynamics? Does > tapestry have any memory leaks? > > thanks > > Joe > > _________________________________________________________________ > Send and receive Hotmail on your mobile device: http://mobile.msn.com > > > _______________________________________________ > Tapestry-developer mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/tapestry-developer _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
