JDK-6341455 : os::write_memory_serialize_page need a explicit handler in thread native transition
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 5.0u3
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2005-10-25
  • Updated: 2012-10-08
  • Resolved: 2005-11-10
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other JDK 6
5.0u8Fixed 6 b60Fixed
Related Reports
Relates :  
JDK-6305157 - multiple Java threads are using JNI C++ method concurrently, access violations thrown. regression?
Relates :  
JDK-2135479 - WIN64: VM should not use Vectored Exceptions
Relates :  
JDK-6354368 - Japanese IME crashes JVM on J2SE 1.5 for WindowsXP 64 bit edition
Description
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.
Comments
EVALUATION We wrap access to serialize page with __try/_except clause, with trivial handler, to handle access faults. This has no significant performance effect even on JNI microbenchmarks.
03-11-2005