RFR: 8373945: vmTestbase eatMemory/ClassUnloader provoke OOME to force GC and might cause GC in other threads [v3]
SendaoYan
syan at openjdk.org
Fri Dec 19 06:43:36 UTC 2025
> 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:
>
> - [ ] All jtreg tests by fastdebug build
SendaoYan has updated the pull request incrementally with one additional commit since the last revision:
Update test/hotspot/jtreg/vmTestbase/gc/gctests/LargeObjects 5 tests
-------------
Changes:
- all: https://git.openjdk.org/jdk/pull/28891/files
- new: https://git.openjdk.org/jdk/pull/28891/files/3028bbea..7e67804f
Webrevs:
- full: https://webrevs.openjdk.org/?repo=jdk&pr=28891&range=02
- incr: https://webrevs.openjdk.org/?repo=jdk&pr=28891&range=01-02
Stats: 18 lines in 5 files changed: 16 ins; 0 del; 2 mod
Patch: https://git.openjdk.org/jdk/pull/28891.diff
Fetch: git fetch https://git.openjdk.org/jdk.git pull/28891/head:pull/28891
PR: https://git.openjdk.org/jdk/pull/28891
More information about the serviceability-dev
mailing list