RFR: 8369150: NMethodRelocationTest fails when JVMTI events not published before JVM exit [v6]

David Holmes dholmes at openjdk.org
Mon Jan 12 22:21:44 UTC 2026


On Tue, 6 Jan 2026 22:47:08 GMT, Chad Rakoczy <duke at openjdk.org> wrote:

>> [JDK-8369150](https://bugs.openjdk.org/browse/JDK-8369150)
>> 
>> The test checks for JVMTI `COMPILED_METHOD_LOAD` and `COMPILED_METHOD_UNLOAD` events to be published for a relocated nmethod. It would originally intermittently fail if the JVM exited before it had time to publish the events so now it loops and forces GCs to encourage event publishing. The test fails if the events are received in the incorrect order (such as an unload before a load) or if the correct events are not received and the test times out.
>
> Chad Rakoczy has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Remove JNIenv use and update shouldExit

After this change the test is failing with:

<COMPILED_METHOD_LOAD>:   name: compiledMethod, code: 0x0000ffff6c9ed5c0
<COMPILED_METHOD_LOAD>:   name: compiledMethod, code: 0x0000ffff6c9f4840
check_jvmti_error: JVMTI function returned error: get_method_name: error in JVMTI GetMethodName call: JVMTI_ERROR_INVALID_METHODID(23)

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

PR Comment: https://git.openjdk.org/jdk/pull/28683#issuecomment-3740777629


More information about the serviceability-dev mailing list