Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8194599 | 11 | David Holmes | P4 | Resolved | Fixed | b01 |
JDK-8299519 | 8u371 | Dukebot | P4 | Resolved | Fixed | b01 |
One result is that EnsureLocalCapacity calls can be ineffective for preventing the local ref warning issued under -Xcheck:jni ("WARNING: JNI local refs: XX, exceeds capacity: YY") because the request is "forgotten" due to subsequent (sometimes tricky to spot) calls to EnsureLocalCapacity.
The attached test case demonstrates the problem when run with -Xcheck:jni.
- backported by
-
JDK-8194599 EnsureLocalCapacity() should maintain capacity requests through multiple calls
- Resolved
-
JDK-8299519 EnsureLocalCapacity() should maintain capacity requests through multiple calls
- Resolved
- relates to
-
JDK-8225217 Backout: JDK-8224814: Remove dead JNIHandleBlock freelist code
- Resolved
-
JDK-8297106 Remove the -Xcheck:jni local reference capacity checking
- Resolved
-
JDK-8193271 ProblemList tools/launcher/TestXcheckJNIWarnings.java
- Resolved
-
JDK-8193460 Take tools/launcher/TestXcheckJNIWarnings.java back off the ProblemList
- Resolved
-
JDK-8231769 Test tools/javac/tree/MakeTypeTest.java fails with -Xcheck:jni
- Resolved
-
JDK-8043224 -Xcheck:jni improvements to exception checking and excessive local refs
- Closed
-
JDK-8296936 -Xcheck:jni creates WARNING: JNI local refs: xxx, exceeds capacity: 32 with jdwp agent active
- Closed