RFR: 8313816: Accessing jmethodID might lead to spurious crashes [v10]
Coleen Phillimore
coleenp at openjdk.org
Wed Nov 29 17:18:15 UTC 2023
On Wed, 29 Nov 2023 15:14:59 GMT, Jaroslav Bachorik <jbachorik at openjdk.org> wrote:
>> I am going to take a look.
>
> Ok, I found it.
> The reason for the jmethodID not being cleaned out is this assignment of a new jmethodID to obsolete methods - https://github.com/openjdk/jdk/blob/a2c5f1fc914ef5c28d044b75598f895cf6097138/src/hotspot/share/prims/jvmtiRedefineClasses.cpp#L3887
>
> Since this is not done for EMCP (or more generic, non-obsolete) methods restricting the cleanup process to obsolete methods still sounds like the right thing to do.
Excellent thanks.
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/16662#discussion_r1409626840
More information about the serviceability-dev
mailing list