https://issues.apache.org/bugzilla/show_bug.cgi?id=51195
--- Comment #6 from Joern Huxhorn <jhuxh...@googlemail.com> 2011-05-24 11:09:57 UTC --- I disagree. The cleanup performed in the code is merely to prevent a *false* memory leak warning. A real leak does, in fact, not exist. This is the reason why I put it directly before the execution of System.gc() in the "Find Leaks" function. Since "Find Leaks" isn't supposed to be executed in a production environment, I don't think that any further optimization (suggestion in 2.) makes sense. It would probably make sense if this code would indeed be added to the normal undeploy procedure but I really don't think that this is necessary or advisable. The idea is to prevent false memory leak warnings so that real ones aren't ignored if they occur. See http://en.wikipedia.org/wiki/The_Boy_Who_Cried_Wolf ;) -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
