Details
-
Enhancement
-
Resolution: Fixed
-
P3
-
11, 17, 19
-
b03
Description
A comment in the CR also states that:
"We decided that we will change the marking to simply expand the global mark stack when it goes out of memory, until MarkStackSizeMax. We will exit the VM if that is not enough global mark stack memory available for processing. We will remove the re-scan of the region as it is already complicated enough and adding the condition that we rescan only outside of weak reference processing makes it even worse. "
This has not implemented until now as
Attachments
Issue Links
- duplicates
-
JDK-8313212 G1: Intermittent mark stack overflow during reference processing
- Resolved
-
JDK-8312534 [linux x86] assert in g1ConcurrentMark.cpp: Overflow during reference processing
- Closed
-
JDK-8281647 G1: Overflow during reference processing
- Closed
-
JDK-8315449 JVM crash in g1ConcurrentMark.cpp - fatal error: Overflow during reference processing
- Closed
-
JDK-8204337 Test case for JDK-8202049: G1: ReferenceProcessor doesn't handle mark stack overflow
- Closed
- relates to
-
JDK-8313582 Problemlist failing test on linux x86
- Resolved
-
JDK-8204337 Test case for JDK-8202049: G1: ReferenceProcessor doesn't handle mark stack overflow
- Closed
-
JDK-8325202 gc/g1/TestMarkStackOverflow.java intermittently crash: G1CMMarkStack::ChunkAllocator::allocate_new_chunk
- Resolved
-
JDK-8280029 G1: "Overflow during reference processing, can not continue" on x86_32
- Resolved
-
JDK-8312534 [linux x86] assert in g1ConcurrentMark.cpp: Overflow during reference processing
- Closed
-
JDK-8281647 G1: Overflow during reference processing
- Closed