> The problem happens when jni access fields while the last java frame is still > compiled. The field access/modification events require interp only mode and > compiled frame is not expected. However, It might happens if thread switched > to interponly mode while it is in JNI code. The deoptimization is triggered > but each frame is really changed only execution returns to it. So last java > frame was not executed and thus is still compiled. > > The original example doesn't reproduce issue because of JDK changes but the > problem exists in JVMTI. So I implemented reliable regression test. > > The location should be zero for JNI access.
Leonid Mesnik has updated the pull request incrementally with one additional commit since the last revision: fixed comment ------------- Changes: - all: https://git.openjdk.org/jdk/pull/27584/files - new: https://git.openjdk.org/jdk/pull/27584/files/8b18b5bb..bb5837ec Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=27584&range=01 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=27584&range=00-01 Stats: 1 line in 1 file changed: 0 ins; 1 del; 0 mod Patch: https://git.openjdk.org/jdk/pull/27584.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/27584/head:pull/27584 PR: https://git.openjdk.org/jdk/pull/27584
