Loading...

XML

Word

Printable

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

Subcomponent:
gc
Resolved In Build:
b15
Verification:
Verified

Issue	Fix Version	Assignee	Priority	Status	Resolution	Resolved In Build
JDK-8045458	8u25	Per Liden	P2	Resolved	Fixed	b01
JDK-8043121	8u20	Per Liden	P2	Closed	Fixed	b17
JDK-8053372	emb-8u26	Per Liden	P2	Resolved	Fixed	b17

Concurrent mark threads use os::elapsedVTime() to regulate its CPU usage over time. However, it seems that these threads can get stuck in a loop calling os::elapsedVTime() over and over without making any progress, which causes the whole marking concurrent phase to hang.

backported by

JDK-8045458 G1: Concurrent mark stuck in loop calling os::elapsedVTime()

Resolved

JDK-8053372 G1: Concurrent mark stuck in loop calling os::elapsedVTime()

Resolved

JDK-8043121 G1: Concurrent mark stuck in loop calling os::elapsedVTime()

Closed

blocks

JDK-8040807 G1: Enable G1CollectedHeap::stop()

Resolved

JDK-8044795 G1: Enable G1CollectedHeap::stop()

Closed

relates to

JDK-8013895 G1: G1SummarizeRSetStats output on Linux needs improvement

Resolved

JDK-8040245 G1: VM hangs during shutdown

Closed

(2 relates to)

Assignee:: Per Liden (Inactive)

Reporter:: Per Liden (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: 2014-04-17 04:53

Updated:: 2017-07-26 14:09

Resolved:: 2014-05-14 06:17

Details

Backports

Description

Attachments

Issue Links

Activity

People

Dates