Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P2
Fix Version/s: 9
Affects Version/s: 9
Component/s: hotspot
Labels:
- gc-g1

Subcomponent:
gc
Resolved In Build:
b159
Verification:
Verified

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-8176693	10	Kim Barrett	P2	Resolved	Fixed	b03

After discussions around possible weak reference object resurrection through Unsafe::getObjectVolatile it was realized that weak JNI handles suffer from the same problem.
Code dereferencing a jweak must ensure that the oop is marked by SATB since the jweak may have been the only remaining reference to the object.

Unfortunately the JNI spec allows jweak parameters in place of any jobject parameter to any JNI entry point so we would either need to be able to detect a jweak parameter or unconditionally ensure that all resolved objects are marked.

backported by

JDK-8176693 G1 Needs pre barrier on dereference of weak JNI handles

Resolved

is blocked by

JDK-8169517 WhiteBox should provide concurrent GC phase control

Resolved

relates to

JDK-8175086 [BACKOUT] fix for JDK-8166188

Resolved

JDK-8176101 CLONE - [BACKOUT] fix for JDK-8166188

Closed

JDK-8173013 JVMTI tagged object access needs G1 pre-barrier

Resolved

JDK-8175085 [REDO] G1 Needs pre barrier on dereference of weak JNI handles

Closed

JDK-8176100 [REDO][REDO] G1 Needs pre barrier on dereference of weak JNI handles

Closed

JDK-8178813 Add test for G1 pre-barrier on dereference of weak JNI handles

Resolved

JDK-8176325 Failures in g1HeapVerifier.cpp

Closed

(4 relates to)

Assignee:: Kim Barrett

Reporter:: Mikael Gerdin (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 7 Start watching this issue

Created:: 2016-09-16 01:51

Updated:: 2017-07-26 14:18

Resolved:: 2017-02-15 20:31

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates