On 16/02/2016 22:07, Ty wrote: >> Exactly which versions were you using when you ran your tests? > > According to my notes: 7.0.59, which should've been the most recent > version available at the time (about this time last year). > > To clarify: that was the version we did a heap dump analysis of, and noted > the memory increase related to Manifest objects. The version used for the > test procedure in this thread's original message -- last performed last > week -- was 7.0.67 and we did not do a heap analysis of it (only noting > that at a glance it resulted in approximately the same amount of heap > increase correlating with JAR scanning as we saw with last year's version).
Thanks for the version info. I've started looking at this. The bulk of the memory is used by JarResourceSet. It is caching a JarFileEntry object for each class in the JAR. I wrote this code but I don't recall why those entries were retained. I need to look back through svn to figure out what problem it was solving and then see if I can find a better solution. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
