JDK-8057722 : G1: Code root hashtable updated incorrectly when evacuation failed
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 9
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2014-09-05
  • Updated: 2017-07-26
  • Resolved: 2014-09-09
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
8u40Fixed 9 b32Fixed
Related Reports
Duplicate :  
assert(!_g1h->obj_in_cs(o) || hr->rem_set()->strong_code_roots_list_contains(_nm)) failed: if o still in CS then evacuation failed and nm must already be in the remset

Failed in gc-nightly 2014-09-04
Regression test exists.

The condition for keeping nmethods in the remembered set when processing evacuation failures was inverted. Additionally, the size accounting of remembered sets post-evacuation failures was incorrect.

ILW: I: high -> assertion failure L: low -> only test case, only win32, fastdebug only W: high -> unknown