-
1. Re: Stripped down reference reports from JVMTIInterface
brian.stansberry Mar 11, 2007 8:36 PM (in response to brian.stansberry)I've implemented a version of this in the AS testsuite (trunk and Branch_4_2). See org.jboss.test.classloader.leak.clstore.LeakAnalyzer. Added an overloaded exploreObjectReferences that takes a parameter to indicate if it should produce a condensed format report. If not condensed, reference chains that would survive on the condensed report are shown in bold, with the ultimate root in red.
Not sure at this point if the condensed part works right, but the bold/red bit does, so I know I can make the condensed work simply by not printing nodes if they wouldn't be bold. I'll do that sometime later. -
2. Re: Stripped down reference reports from JVMTIInterface
starksm64 Mar 12, 2007 4:00 AM (in response to brian.stansberry)This looks great. I got the ClassloaderLeakUnitTestCase.testSimpleWar passing by clearing the WebMetaData class loader refs the report showed. The associated root was a ThreadLocal entry that I currently don't see how could exist. Its cleared at the end of every request so either I'm missng somethng or there is another one in the thirdparty layer.
-
3. Re: Stripped down reference reports from JVMTIInterface
clebert.suconic Mar 12, 2007 11:48 AM (in response to brian.stansberry)"bstansberry@jboss.com" wrote:
I've implemented a version of this in the AS testsuite (trunk and Branch_4_2). See org.jboss.test.classloader.leak.clstore.LeakAnalyzer. Added an overloaded exploreObjectReferences that takes a parameter to indicate if it should produce a condensed format report. If not condensed, reference chains that would survive on the condensed report are shown in bold, with the ultimate root in red.
Not sure at this point if the condensed part works right, but the bold/red bit does, so I know I can make the condensed work simply by not printing nodes if they wouldn't be bold. I'll do that sometime later.
I will copy the method to JVMTIInterface.