On Tue, 18 Feb 2025 23:38:35 GMT, Chris Plummer <cjplum...@openjdk.org> wrote:
>> When doing a STEP_OVER, the debug agent does a NotifyFramePop() on the >> current frame as a safety net. After the STEP_OVER completes, the >> NotifyFramePop() is usually still in place. This keeps the thread in >> interp_only mode, which hurts performance. JVMTI has added a new >> ClearAllFramePops() API to allow clearing of the NotifyFramePop() and normal >> performance to resume. >> >> Testing: >> >> - [x] Tier1 CI >> - [x] Tier2 CI svc testing >> - [x] Tier3 CI svc testing >> - [x] Tier5 CI svc testing >> - [x] ran all svc test 10 times each on all supported platforms > > Chris Plummer has updated the pull request incrementally with one additional > commit since the last revision: > > get rid of redundant if I filed [JDK-8350368](https://bugs.openjdk.org/browse/JDK-8350368) to address the clearStep() locking issue. ------------- PR Comment: https://git.openjdk.org/jdk/pull/23182#issuecomment-2669296694
