JDK-8213142 : Use RAII to set the scanning source in G1ScanEvacuatedObjClosure
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 12
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2018-10-30
  • Updated: 2021-08-30
  • Resolved: 2018-10-31
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.
JDK 12
12 b18Fixed
Related Reports
Blocks :  
JDK-8212911 - Unify and micro-optimize handling of non-in-collection set references in oop closures
Relates :  
JDK-8265409 - Crash on building LineageOS with Problematic frame: # V [libjvm.so+0x6a1fe3] void G1ScanEvacuatedObjClosure::do_oop_work
Relates :  
JDK-8248892 - JVM Crashed in G1ScanEvacuatedObjClosure::do_oop_work | OpenJDK build 11.0.7+10-LTS
Relates :  
JDK-8273137 - Improve skipping card enqueuing during gc if there are no remembered sets in old gen
Description
G1ScanEvacuatedObjClosure needs to be told where the object that is scanned is located (young/old) to properly handle additions to the remembered sets.

Currently we call a method on G1ScanEvacuatedObjClosure to do so, but it would be better to use an RAII object that automatically sets and resets it. With an additional "Uninitialized" state, basic checking whether the value has been set to find bugs can be implemented easily too.

Suggested by ~kbarrett in the review thread for JDK-8212911.
Comments
URL: http://hg.openjdk.java.net/jdk/jdk/rev/f34a2e0069c7 User: tschatzl Date: 2018-10-31 12:44:27 +0000
31-10-2018