Loading...

XML

Word

Printable

Type: Enhancement
Resolution: Fixed
Priority: P4
Fix Version/s: 9
Affects Version/s: 8u40, 9
Component/s: hotspot
Labels:

Subcomponent:
gc
Resolved In Build:
b26

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-8056676	emb-9	Unassigned	P4	Resolved	Fixed	b26
JDK-8063377	8u45	Thomas Schatzl	P4	Resolved	Fixed	b01
JDK-8051705	8u40	Thomas Schatzl	P4	Resolved	Fixed	b02
JDK-8070857	emb-8u47	Thomas Schatzl	P4	Resolved	Fixed	team

If before a full GC (that is already in the vm operation queue) a GC Remark happens, the VM continues to clear the next bitmap although it has already been cleared when aborting it.

This is additional, needless work. Guard the call to _cm->clearNextBitmap() in ConcurrentMarkThread::run() with the appropriate condition.

backported by

JDK-8051705 Aborting marking just before remark results in useless additional clearing of the next mark bitmap

Resolved

JDK-8056676 Aborting marking just before remark results in useless additional clearing of the next mark bitmap

Resolved

JDK-8063377 Aborting marking just before remark results in useless additional clearing of the next mark bitmap

Resolved

JDK-8070857 Aborting marking just before remark results in useless additional clearing of the next mark bitmap

Resolved

relates to

JDK-8054808 Bitmap verification sometimes fails after Full GC aborts concurrent marking

Resolved

JDK-7098512 G1: Do not clear the next marking bitmap at the start of a Full GC

Closed

JDK-8038423 G1: Decommit memory within the heap

Resolved

(2 relates to)

Assignee:: Thomas Schatzl
Reporter:: Thomas Schatzl
Votes:: 0 Vote for this issue
Watchers:: 2 Start watching this issue

Created:: 2014-06-25 03:36
Updated:: 2015-01-21 09:46
Resolved:: 2014-07-21 03:11

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates