On Tue, 23 Dec 2025 07:32:47 GMT, SendaoYan <[email protected]> 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: >> >> - [ ] All jtreg tests by fastdebug build > > SendaoYan has updated the pull request incrementally with one additional > commit since the last revision: > > Update commnets for ClassUnloader Something strange is going on with this PR. I just get 3 separate emails for each of the following commits that were done in the past day: - [Fix the copy-n-paste error](https://github.com/openjdk/jdk/pull/28891/changes/349ae833fb600ab9136ab4f43749d1e5f2c84ca0) - [Update commnets for ClassUnloader](https://github.com/openjdk/jdk/pull/28891/changes/6c144309a091038aaed1d698bd12323f3672c7b9) - [Remove unnecessary catch OOME in gc/gctests/LargeObjects/large001/large001.java](https://github.com/openjdk/jdk/pull/28891/changes/e8d128e666ee0a8cbbf6d9dc273636b62bd3fb96) However, the PR claims that these commits were all done on Nov 22, not Dec. ------------- PR Comment: https://git.openjdk.org/jdk/pull/28891#issuecomment-3687093047
