On Fri, 11 Oct 2024 08:39:42 GMT, Serguei Spitsyn <sspit...@openjdk.org> wrote:
> There is a race between JVMTI NotifyFramePop function and FramePop event > posting code. > The fix is to return JVMTI_ERROR_OPAQUE_FRAME if if a FramePop event with > depth 0 is requested by NotifyFramePop at the time when the target frame is > in exit epilogue, and MethodExit/FramePop events are being posted for it. > > Testing: > - verified locally with new test (developed by Chris): > `serviceability/jvmti/events/NotifyFramePopStressTest` > - TBD: mach5 tiers 1-6 This pull request has now been integrated. Changeset: 85911094 Author: Serguei Spitsyn <sspit...@openjdk.org> URL: https://git.openjdk.org/jdk/commit/8591109419efc8f71544a98bdb04a48cb1afc47e Stats: 340 lines in 6 files changed: 339 ins; 0 del; 1 mod 8340698: JVMTI FRAME_POP event is sometimes missed if NotifyFramePop is called as a method is returning Reviewed-by: cjplummer, amenkov ------------- PR: https://git.openjdk.org/jdk/pull/21468
