RFR: 8334771: [TESTBUG] Run TestDockerMemoryMetrics.java with -Xcomp fails exitValue = 137

SendaoYan syan at openjdk.org
Thu Jul 18 11:44:34 UTC 2024


On Mon, 24 Jun 2024 16:16:29 GMT, SendaoYan <syan at openjdk.org> wrote:

> Hi all,
>   After [JDK-8294960](https://bugs.openjdk.org/browse/JDK-8294960), the footprint memory usage increased significantly when run the testcase with -Xcomp jvm options, then cause the testcase was killed by docker by OOM.
>   Maybe the footprint memory usage increased was inevitable, so I think we should increase the smallest memory limite for this testcase.
>   Only change the testcase, the change has been verified, no risk.

> Unfortunately I'm not familiar with these tests.

> After [JDK-8294960](https://bugs.openjdk.org/browse/JDK-8294960), the codecache usage increased significantly, non-profiled 3068Kb->3583Kb, profiled 6408Kb->7846Kb.

Can you confirm that the codecache usage increased is expected or not after [JDK-8294960](https://bugs.openjdk.org/browse/JDK-8294960) with -Xcomp jvm option.

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

PR Comment: https://git.openjdk.org/jdk/pull/19864#issuecomment-2236291264


More information about the serviceability-dev mailing list