RFR: 8229012: When single stepping, the debug agent can cause the thread to remain in interpreter mode after single stepping completes [v5]
    Chris Plummer 
    cjplummer at openjdk.org
       
    Tue Feb 18 23:38:35 UTC 2025
    
    
  
> 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
-------------
Changes:
  - all: https://git.openjdk.org/jdk/pull/23182/files
  - new: https://git.openjdk.org/jdk/pull/23182/files/bbd778fc..864671ca
Webrevs:
 - full: https://webrevs.openjdk.org/?repo=jdk&pr=23182&range=04
 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=23182&range=03-04
  Stats: 3 lines in 1 file changed: 0 ins; 3 del; 0 mod
  Patch: https://git.openjdk.org/jdk/pull/23182.diff
  Fetch: git fetch https://git.openjdk.org/jdk.git pull/23182/head:pull/23182
PR: https://git.openjdk.org/jdk/pull/23182
    
    
More information about the serviceability-dev
mailing list