RFR 8151486 : Class.forName causes memory leak

Brent Christian brent.christian at oracle.com
Fri Oct 7 18:25:53 UTC 2016

On 10/5/16 4:43 PM, David Holmes wrote:
>>> Okay but this will still affect the lifecycle of the PDs because
>>> without the strong reference in L, those weak references in the VM
>>> will quickly be cleared.

There's also a strong reference held by the Class object itself (on the 
VM side [1]).

Thanks for having a look, folks.  I've applied Naoto and Mandy's 
suggestions for the test case and updated the webrev in place with what 
I plan to push.




More information about the core-libs-dev mailing list