Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P4
Fix Version/s: hs18
Affects Version/s: hs18
Component/s: hotspot
Labels:
- verify-waive-setup
- zero

Subcomponent:
runtime
Resolved In Build:
b03
CPU:

generic
OS:

generic

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-2191964	7	Christian Thalinger	P4	Closed	Fixed	b90
JDK-2198000	6u23	Christian Thalinger	P4	Closed	Fixed	b01
JDK-2199950	6u22m	Christian Thalinger	P4	Closed	Fixed	b01
JDK-2193534	6u21p	Christian Thalinger	P4	Closed	Fixed	b03

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

backported by

JDK-2191964 Zero locking fix

Closed

JDK-2193534 Zero locking fix

Closed

JDK-2198000 Zero locking fix

Closed

JDK-2199950 Zero locking fix

Closed

relates to

JDK-6962193 Rebrand some Zero files

Resolved

JDK-6908267 Zero fails to unlock synchronized native methods on exception

Closed

(1 relates to)

Assignee:: Christian Thalinger (Inactive)

Reporter:: Christian Thalinger (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 0 Start watching this issue

Created:: 2010-03-30 00:46

Updated:: 2012-10-08 00:51

Resolved:: 2010-04-20 21:55

Imported:: 17/Sep/12 7:33 AM

Indexed:: 19/Jul/12 10:38 PM

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates