Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P3
Fix Version/s: hs20
Affects Version/s: hs19, 6, 6u4
Component/s: hotspot
Labels:

Subcomponent:
gc
Introduced In Build:
1.4.2
Introduced In Version:

1.4.2
Resolved In Build:
b02
CPU:

generic, x86
OS:

generic, solaris_10
Verification:
Not verified

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-2202396	7	Y. Ramakrishna	P3	Resolved	Fixed	b118
JDK-2205875	6u25	Y. Ramakrishna	P3	Resolved	Fixed	b01

This can result in unnecessarily pessimistic initial bailout to a
full collection (concurrent mode failure) when a scavenge would in fact
have provably succeeded at the point at which the decision to bail out was made.
See related email in comments section.
Synopsis changed from:-

CMS/GCH: collection_attempt_is_safe() ergo should use more recent data

to:-

CMS/GCH: incremental_collection_will_fail() should use more current data

backported by

JDK-2202396 CMS/GCH: incremental_collection_will_fail() should use more current data

Resolved

JDK-2205875 CMS/GCH: incremental_collection_will_fail() should use more current data

Resolved

duplicates

JDK-6261660 CMS promotion failure & gc_locker induced GC malinteraction

Closed

JDK-6990095 Deprecate and eliminate -XX:-HandlePromotionFailure

Closed

relates to

JDK-6995045 assert(!gch->incremental_collection_failed()) failed: Error, defNewGeneration.cpp:827

Resolved

Assignee:: Y. Ramakrishna

Reporter:: Y. Ramakrishna

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2009-10-29 17:04

Updated:: 2011-04-20 03:41

Resolved:: 2011-04-20 03:41

Imported:: 17/Sep/12 3:27 AM

Indexed:: 19/Jul/12 7:33 PM

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates