> 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
Serguei Spitsyn has updated the pull request incrementally with one additional commit since the last revision: review test tweaks: add @bug tag; a reliability update ------------- Changes: - all: https://git.openjdk.org/jdk/pull/21468/files - new: https://git.openjdk.org/jdk/pull/21468/files/3b82454f..dc457681 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=21468&range=04 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=21468&range=03-04 Stats: 12 lines in 2 files changed: 4 ins; 3 del; 5 mod Patch: https://git.openjdk.org/jdk/pull/21468.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/21468/head:pull/21468 PR: https://git.openjdk.org/jdk/pull/21468
