-
Bug
-
Resolution: Fixed
-
P3
-
5.0, 6
-
b40
-
generic, sparc
-
generic, solaris
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2126497 | 5.0u8 | Kumar Srinivasan | P3 | Closed | Won't Fix |
that we do not enter JNI while an exception is pending. If
there is a pending exception and a customer is using -Xcheck:jni,
the VM will exit with a fatal error.
This check in general is a good idea, however since the introduction of
this check, we have encountered several instances in the J2SE libraries
and customer libraries where this condition is true.
The fact that the VM is exiting when this occurs is prohibiting the
continued checking of native code. Most if not all cases that we've
encuntered have been benign and it would have been more beneficial
to simply provide a warning and continue executing.
###@###.### 2005-04-11 17:19:48 GMT
- backported by
-
JDK-2126497 -Xcheck:jni JNI call made with exception pending should be a warning
-
- Closed
-
- duplicates
-
JDK-6369565 JVM is crashing when it is not able to determine current working directory
-
- Closed
-
- relates to
-
JDK-6760147 java programs are not usable when current directory is unknown
-
- Closed
-
-
JDK-6382189 REGRESSION:JPEGMultithread.java is passing with 1.5.0_06-b05 but failing with 1.5.0_07-b01
-
- Closed
-
-
JDK-6307699 regression at 1.6.0 b46 for alacrity jetstream client on XP-x86 (8%) and Linux-x86 (2%)
-
- Closed
-
-
JDK-2134110 Regresssion: com/sun/image/codec/jpeg/JPEGMultithread.java fails
-
- Closed
-