Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8086432 | 8u65 | Poonam Bajaj Parhar | P4 | Resolved | Fixed | b01 |
JDK-8072804 | 8u60 | Poonam Bajaj Parhar | P4 | Resolved | Fixed | b07 |
JDK-8137646 | emb-8u65 | Unassigned | P4 | Resolved | Fixed | b01 |
JDK-8077448 | emb-8u60 | Poonam Bajaj Parhar | P4 | Resolved | Fixed | team |
Description
1) Checked JNI to enforce calling "ExceptionOccurred()" or "ExceptionOccurred()" after using "Call*Method()" functions, before using further JNI functions. Warn if exception check not carried out before calling a method that does not allow pending exceptions. Subtle difference to the current "there is a pending exception" check, does the programmer actual call one of the check functions.
2) If a JNI method implicitly grew the local ref capacity beyond what was planned for, warn the user. This of course excludes PushLocalFrame or EnsureLocalCapacity.
Attachments
Issue Links
- backported by
-
JDK-8072804 -Xcheck:jni improvements to exception checking and excessive local refs
- Resolved
-
JDK-8077448 -Xcheck:jni improvements to exception checking and excessive local refs
- Resolved
-
JDK-8086432 -Xcheck:jni improvements to exception checking and excessive local refs
- Resolved
-
JDK-8137646 -Xcheck:jni improvements to exception checking and excessive local refs
- Resolved
- duplicates
-
JDK-6723450 -verbose:jni or -Xcheck:jni do not report excessive local reference usage.
- Resolved
- relates to
-
JDK-8164086 Checked JNI pending exception check should be cleared when returning to Java frame
- Resolved
-
JDK-8046668 Excessive checked JNI warnings from Java startup
- Closed
-
JDK-8193222 EnsureLocalCapacity() should maintain capacity requests through multiple calls
- Resolved
-
JDK-8160614 Some of the checked JNI improvements are excessively verbose
- Closed