-
Bug
-
Resolution: Fixed
-
P3
-
5.0u3
-
b60
-
x86
-
windows_xp
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2135480 | 5.0u8 | Steve Bohne | P4 | Closed | Fixed | b01 |
When JVM issues write_memroy_serialize_page, an access violation will be generated then handled by exception filter handler, but if customer has JNI code and use MS C++ like
try {
// java method invoke
// others
}
catch(...) {
// user handling code
}
When this fault happens in the try block, it will be caught in user handling block and usually user has no idea what this fault is so the process messed up, terminated. An explicit handling needed in JVM so user code will not catch it.
See bug 5075546 and 6305157 for details.
try {
// java method invoke
// others
}
catch(...) {
// user handling code
}
When this fault happens in the try block, it will be caught in user handling block and usually user has no idea what this fault is so the process messed up, terminated. An explicit handling needed in JVM so user code will not catch it.
See bug 5075546 and 6305157 for details.
- backported by
-
JDK-2135480 os::write_memory_serialize_page need a explicit handler in thread native transition
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-