JDK-5075546 : remove memory barrier on native transitions
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 6
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2004-07-19
  • Updated: 2012-10-08
  • Resolved: 2004-09-14
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.0u3Fixed 6 mustangFixed
Related Reports
Relates :  
JDK-6305157 - multiple Java threads are using JNI C++ method concurrently, access violations thrown. regression?
Relates :  
JDK-6279018 - Remove diagnostic -XX:+UseMembar flag
Description
In J2SE 1.4.2 a memory barrier instruction was added whenever most
thread state transitions are performed in order to fix a bug were
a race condition could allow a thread to escape from blocking
during a safepoint operation.  The addition of the memory barrier
has added substantial overhead to all JNI, VM and calling native
functions.
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: dragon mustang FIXED IN: mustang INTEGRATED IN: mustang
15-09-2004
PUBLIC COMMENTS Integrated in Build 04
15-09-2004
EVALUATION This bug is a place holder for this 1.5.1 improvement. ###@###.### 2004-07-20 The memory barriers that were added in 1.4.2 have been removed and replaced with a new mprotect based scheme. ###@###.### 2004-09-07
20-07-2004