JDK-6939180 : Zero locking fix
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: hs18
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2010-03-30
  • Updated: 2012-10-08
  • Resolved: 2010-04-21
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.
JDK 6 JDK 7 Other
6u21pFixed 7Fixed hs18Fixed
Related Reports
Relates :  
JDK-6908267 - Zero fails to unlock synchronized native methods on exception
Description
Gary Benson wrote:

Hi all,

When Zero is running with Shark enabled threads can be left with
their _do_not_unlock_if_synchronized flag incorrectly set.  This
flag is unnecessary in Zero, and should have been removed as part
of the fix for 6908267 but sadly I missed it!

  http://cr.openjdk.java.net/~gbenson/zero-locking-fix/

I don't have a bug id for this.

Cheers,
Gary
Comments
EVALUATION http://hg.openjdk.java.net/jdk7/hotspot-rt/hotspot/rev/747d26efc5fa
08-04-2010
EVALUATION http://hg.openjdk.java.net/jdk7/hotspot-comp/hotspot/rev/747d26efc5fa
30-03-2010