Loading...

XML

Word

Printable

Type: Enhancement
Resolution: Won't Fix
Priority: P3
Fix Version/s: hs18
Affects Version/s: 6, 6u6, 6u14, 6u20
Component/s: hotspot
Labels:
- sust:tct
- verify-waive-setup

Subcomponent:
gc
CPU:

generic, unknown, x86
OS:

generic, linux_2.4, windows

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-2201449	7	John Coomes	P3	Closed	Fixed	b115
JDK-2205786	6u25	John Coomes	P3	Closed	Fixed	b01
JDK-2201491	6u23	John Coomes	P3	Resolved	Fixed	b02
JDK-2191954	6u21	John Coomes	P3	Resolved	Fixed	b03
JDK-2187572	6u19	Chris Phillips	P3	Closed	Fixed	b02
JDK-2189210	6u18-rev	Chris Phillips	P3	Resolved	Fixed	b09
JDK-2183140	6u17-rev	Chris Phillips	P3	Resolved	Fixed	b07
JDK-2200300	hs20	John Coomes	P3	Closed	Fixed	b02
JDK-2200150	hs19	John Coomes	P3	Closed	Fixed	b09
JDK-2191800	hs17	John Coomes	P3	Closed	Fixed	b13
JDK-2187571	hs16.2	Chris Phillips	P3	Resolved	Fixed	b02
JDK-2187641	hs16.1	Chris Phillips	P3	Resolved	Fixed	b02
JDK-2186575	hs14.3	Chris Phillips	P3	Resolved	Fixed	b03

The marking stack used by MarkSweep currently uses a GrowableArray<oop>. That's overkill, since we only use the marking stack as a stack. In contrast, GrowableArray implements an array, so when it expands, it reallocs and copies the whole array to a new, larger, piece of contiguous memory. Since the marking stack is often large, this often requires a large contiguous chunk of memory, which can be difficult to acquire. Since GrowableArray grows by doubling, on average 25% of the array will be empty. When the marking stack is large, this can be a substantial waste of space.

Instead, the stack could be implemented as a chained series of small regions. This could allow us to balance the storage for the chain pointers against the increment of growth, to use an appropriate amount of space in modest chunks.

backported by

JDK-2183140 GC stacks should use a better data structure

Resolved

JDK-2186575 GC stacks should use a better data structure

Resolved

JDK-2187571 GC stacks should use a better data structure

Resolved

JDK-2187641 GC stacks should use a better data structure

Resolved

JDK-2189210 GC stacks should use a better data structure

Resolved

JDK-2191954 GC stacks should use a better data structure

Resolved

JDK-2201491 GC stacks should use a better data structure

Resolved

JDK-2187572 GC stacks should use a better data structure

Closed

JDK-2191800 GC stacks should use a better data structure

Closed

JDK-2200150 GC stacks should use a better data structure

Closed

JDK-2200300 GC stacks should use a better data structure

Closed

JDK-2201449 GC stacks should use a better data structure

Closed

JDK-2205786 GC stacks should use a better data structure

Closed

duplicates

JDK-6405799 JVM Exits with OutOfMemoryError for vm\utilities\growableArray.cpp

Closed

relates to

JDK-6942771 SEGV in ParScanThreadState::take_from_overflow_stack

Closed

JDK-6988210 gc/gctests/ManyObjects VM crashes with growableArray.cpp. Out of swap space?

Closed

JDK-6935839 excessive marking stack growth during full gcs

Resolved

JDK-6988678 fatal error deadlock handling was unintentionally disabled

Closed

JDK-2191789 SEGV in ParScanThreadState::take_from_overflow_stack

Closed

JDK-2200149 SEGV in ParScanThreadState::take_from_overflow_stack

Closed

(8 backported by, 1 duplicates, 6 relates to)

Assignee:: John Coomes (Inactive)

Reporter:: Peter Kessler

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 2006-05-08 16:47

Updated:: 2011-03-25 13:48

Resolved:: 2011-03-25 13:48

Imported:: 17/Sep/12 2:50 AM

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

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates