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

Jaikiran Pai jpai at openjdk.org
Fri Jul 19 04:06:42 UTC 2024


On Thu, 18 Jul 2024 11:42:17 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.

@sendaoYan, Given Adam's inputs and the reviews you have had for this change, I think you should be able to go ahead and integrate this.

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

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


More information about the serviceability-dev mailing list