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

[Chris Plummer]

On Wed, 24 Dec 2025 08:22:58 GMT, SendaoYan <syan at openjdk.org> wrote:

>> Hi all,
>> 
>> This PR use `WhiteBox.getWhiteBox().fullGC()` instead of `eatMemory` to grigger full GC. The OOME trigger by `eatMemory` may cause vmTestbase/nsk/monitoring/stress/classload tests intermittent fails when run those tests simultancely on some machines. The WB.fullGC() might be use for same purpose. It also reduce test execution time.
>> 
>> Change has been verified locally by running tests vmTestbase/nsk/monitoring/stress/classload on linux-x64.
>> 
>> Additional testing:
>> 
>> - [x] All jtreg tests by fastdebug build
>
> SendaoYan has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Change the copyright year from 2025 to 2026

Changes requested by cjplummer (Reviewer).

test/hotspot/jtreg/vmTestbase/nsk/jvmti/CompiledMethodUnload/compmethunload001.java line 112:

> 110:         int iter = 0;
> 111:         while (num == 0) {
> 112:             // The unload is delayed because it happens asyns

should be "async"

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

PR Review: https://git.openjdk.org/jdk/pull/28891#pullrequestreview-3609731661
PR Review Comment: https://git.openjdk.org/jdk/pull/28891#discussion_r2677442634