Loading...

XML

Word

Printable

Type: Bug
Resolution: Fixed
Priority: P3
Fix Version/s: hs20
Affects Version/s: hs13, hs17, hs19
Component/s: hotspot
Labels:
- gc-g1
- promotion
- sqebug

Subcomponent:
gc
Resolved In Build:
b04
CPU:

generic
OS:

generic
Verification:
Not verified

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-2204340	7	Tony Printezis	P3	Closed	Fixed	b123
JDK-2205837	6u25	Tony Printezis	P3	Resolved	Fixed	b01

While testing a different set of G1 changes I noticed that we seemed to attempt to allocate regions directly into the old gen more often than I was expecting (I was expecting that to happen only when the GC locker is active).

backported by

JDK-2205837 G1: unnecessary direct-to-old allocations

Resolved

JDK-2204340 G1: unnecessary direct-to-old allocations

Closed

duplicates

JDK-6920109 G1: lingering instabilities with ReduceInitialCardMarks

Closed

relates to

JDK-7005799 G1: nsk/regression/b6186200 fails with OOME

Closed

JDK-6910247 G1: Refactor code in g1BlockOffsetTable.[ch]pp with that of other collectors

Closed

JDK-7003860 G1: assert(_cur_alloc_region == NULL || !expect_null_cur_alloc_region) fails

Closed

JDK-6977804 G1: remove the zero-filling thread

Closed

JDK-6994056 G1: when GC locker is active, extend the Eden instead of allocating into the old gen

Closed

JDK-6994322 Remove the is_tlab and is_noref / is_large_noref parameters from the CollectedHeap interface

Closed

JDK-7005808 G1: re-enable ReduceInitialCardMarks for G1

Closed

JDK-7023069 G1: Introduce symmetric locking in the slow allocation path

Closed

(6 relates to)

Assignee:: Tony Printezis
Reporter:: Tony Printezis
Votes:: 0 Vote for this issue
Watchers:: 1 Start watching this issue

Created:: 2010-08-05 10:21
Updated:: 2013-09-18 04:55
Resolved:: 2011-04-23 16:41
Imported:: 17/Sep/12 3:37 AM
Indexed:: 19/Jul/12 7:37 PM

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates