2012/11/6 Christopher Schultz <ch...@christopherschultz.net>: > On 11/6/12 10:37 AM, Konstantin Kolinko wrote: >> 2012/11/6 Christopher Schultz <ch...@christopherschultz.net>: > >> 2) I know of a bug in JVM when a certain kind of leak goes >> undetected. I mean the leak through a shared Exception instance >> and its native stacktrace. See >> >> https://issues.apache.org/bugzilla/show_bug.cgi?id=50460 >> https://issues.apache.org/bugzilla/show_bug.cgi?id=53936 (Linked >> from https://wiki.apache.org/tomcat/MemoryLeakProtection) > > I don't create any of my own Exception objects that get shared. Could > this be something introduced by Tomcat itself, or more likely some > dependent library of mine? > > Since I can't readily trace the WebappClassLoader to its GC roots, do > you have any suggestions for identifying the specific cause in my case? >
IIRC, I found that issue by looking for Exception objects that were present in the memory. I was using Eclipse MAT. IIRC I filtered the living objects by their class name. Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
