JDK-8289822 : G1: Make concurrent mark code owner of TAMSes
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 20
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2022-07-06
  • Updated: 2024-03-27
  • Resolved: 2024-03-19
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 23
23 b15Fixed
Related Reports
Blocks :  
Blocks :  
Blocks :  
Relates :  
Relates :  
Relates :  
Description
Currently HeapRegion "owns" the top_at_mark_start (TAMS) member, it is placed within that class.

As such uses have bled all over the place (particular in log messages).

However TAMS is a temporary value only needed for marking - so similar to current marked live bytes it should be managed there.


Comments
Hi, Witnessed a slowdebug jvm crash on linux-aarch64 after this change: https://bugs.openjdk.org/browse/JDK-8328879
25-03-2024

Changeset: f1c69cca Author: Thomas Schatzl <tschatzl@openjdk.org> Date: 2024-03-19 10:31:47 +0000 URL: https://git.openjdk.org/jdk/commit/f1c69ccadb83306d1bb4860ff460a253af99643c
19-03-2024

A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/18150 Date: 2024-03-07 10:31:27 +0000
07-03-2024