JDK-8319980 : [JVMCI] libgraal should reuse Thread instances as C2 does
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 22
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2023-11-13
  • Updated: 2024-02-02
  • Resolved: 2023-11-30
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 22
22 b27Fixed
Related Reports
Duplicate :  
JDK-8318885 - [JVMCI] Reuse java.lang.Thread instances with libgraal
Relates :  
JDK-8324983 - Race in CompileBroker::possibly_add_compiler_threads
Description
While it's true that libgraal could lazily create the java.lang.Threads associated with the compiler threads, doing so exposes it to deadlocks during startup in the presence of -Xcomp or -XX:-BackgroundCompilation
Comments
Changeset: da09eabd Author: Tom Rodriguez <never@openjdk.org> Date: 2023-11-30 14:58:18 +0000 URL: https://git.openjdk.org/jdk/commit/da09eabdfc51599d0a34b07c538fba4009af57c5
30-11-2023
ILW = Lazy creation of java.lang.Thread objects leads to deadlocks, with libgraal and -Xcomp/-XX:-BackgroundCompilation, no workaround but enable background compilation = HLM = P3
14-11-2023
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/16638 Date: 2023-11-13 18:44:38 +0000
13-11-2023