RFR: 8319935: Ensure only one JvmtiThreadState is created for one JavaThread associated with attached native thread [v5]

Man Cao manc at openjdk.org
Tue Nov 28 21:34:20 UTC 2023


On Tue, 28 Nov 2023 20:38:55 GMT, Serguei Spitsyn <sspitsyn at openjdk.org> wrote:

>> @sspitsyn For the above suggestions, it seems cleaner/safer to handle the clean-ups in a separate RFE with full testing including the vthread cases. There are additional comments in https://github.com/openjdk/jdk/pull/16642#issuecomment-1815379890 related to this as well. Those could be handled together and require through testing including the vthread support.
>
> Okay, thanks! I was about to suggest the same as it will simplify the process.
> I've filed the following issue and assigned to myself:
> [8320925](https://bugs.openjdk.org/browse/JDK-8320925 )`assert and cleanup in JvmtiThreadState::state_for_while_locked for thread_oop != nullptr`
> 
> I'll prepare a fix for 22 and hope to get you as a reviewer. :)

Thank you @sspitsyn, I'm interested in reviewing the followup change for [8320925](https://bugs.openjdk.org/browse/JDK-8320925) as well.

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

PR Review Comment: https://git.openjdk.org/jdk/pull/16642#discussion_r1408441239


More information about the serviceability-dev mailing list