RFR: 8373945: vmTestbase eatMemory/ClassUnloader provoke OOME to force GC and might cause GC in other threads [v5]

[SendaoYan]

On Fri, 19 Dec 2025 18:41:58 GMT, Chris Plummer <cjplummer at openjdk.org> wrote:

>> SendaoYan has updated the pull request incrementally with one additional commit since the last revision:
>> 
>>   Increase max iteration for nsk/jvmti/CompiledMethodUnload/compmethunload001/TestDescription.java
>
> test/hotspot/jtreg/vmTestbase/gc/gctests/LargeObjects/large001/large001.java line 154:
> 
>> 152: 
>> 153:                     // Drop all references to the class and try to unload it
>> 154:                     WhiteBox.getWhiteBox().fullGC();
> 
> Just to be clear, this is now no different than the `unloader.unloadClass()` call below in terms of how it is implemented. I wonder why the author originally used eatMemory() here and unloadClass() below.

It seems that, the references is non null at the first time. So it will not unload the classes actually,

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/28891#discussion_r2636777045