-
Bug
-
Resolution: Fixed
-
P2
-
None
-
b18
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8205221 | 11.0.1 | Thomas Schatzl | P2 | Resolved | Fixed | team |
If the mark stack overflows during reference processing, further calls to the is_alive closure may return the wrong value, returning false for an actually live object. (Said overflow and wrong answer can only happen because of soft reference phase1 or finalizer reference processing, as those are the only cases where previously unknown live objects can be found during reference processing.) There doesn't appear to be any mechanism for communicating to reference processing that the is_alive closure is no longer reliable.
- backported by
-
JDK-8205221 G1: ReferenceProcessor doesn't handle mark stack overflow
-
- Resolved
-
- relates to
-
JDK-8204337 Test case for JDK-8202049: G1: ReferenceProcessor doesn't handle mark stack overflow
-
- Closed
-
-
JDK-8201826 G1: Don't invoke WeakProcessor if mark stack has overflowed
-
- Closed
-
-
JDK-8313212 G1: Intermittent mark stack overflow during reference processing
-
- Closed
-