DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=33711>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=33711 ------- Additional Comments From [EMAIL PROTECTED] 2005-04-06 16:43 ------- I had a another look into this, and seems better, but I'm not completely convinced that it is entirely fixed. I can't pin down exactly what is happening, but looks like the very first deployment does not fully undeploy (release all references), but subsequent cycles appear to work correctly. The reason it is odd is because after the first cycle my profiler does not list my "BigServlet" class, but the 20MB it allocates never appears to be released (but for each later cycle the graph shows their heap allocations are released). So, sorry but I can't really give a definite answer. Yes it is a big improvement, but no I can't say it is entirely fixed. My cycle is: 1) visit some application that does a sign-in for SSO 2) use the manager to list the apps 3) memory profiler snapshot 4) drop a leak.war in the web apps folder (auto deploy) 5) visit leak with a browser 6) undeploy leak using manager web app 7) repeat from 2 several times, and compare snaphots as well as graphing various memory stats and heap, etc. Thanks for all the efforts! Kev -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
