RFR: 8366850: Test com/sun/jdi/JdbStopInNotificationThreadTest.java failed [v2]

Chris Plummer cjplummer at openjdk.org
Fri Sep 5 19:23:33 UTC 2025


> In order to make this test run faster, its heap size was reduced to 64m. This proved to be too small resulting in sometimes exceeding 10% usage before the notification can be setup. This meant that once the memory consumption loop started, it never stopped until OOME (it's suppose to stop when 10% usage has been achieved). I tried 128m and that also proved to be too small when using ZGC and -Xcomp. 256m seems to be enough. I tested 10x times on all our debug platforms with ZGC, ZGC + -Xcomp, and G1 + -Xcomp.

Chris Plummer has updated the pull request incrementally with one additional commit since the last revision:

  fix errant problem list edit

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

Changes:
  - all: https://git.openjdk.org/jdk/pull/27126/files
  - new: https://git.openjdk.org/jdk/pull/27126/files/fe077ab5..417c0c2f

Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jdk&pr=27126&range=01
 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=27126&range=00-01

  Stats: 4 lines in 1 file changed: 0 ins; 4 del; 0 mod
  Patch: https://git.openjdk.org/jdk/pull/27126.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/27126/head:pull/27126

PR: https://git.openjdk.org/jdk/pull/27126


More information about the serviceability-dev mailing list