JDK-8318444 : Write details about compilation bailouts into crash reports
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 22
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2023-10-18
  • Updated: 2024-02-21
  • Resolved: 2024-01-08
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 b05Fixed
Related Reports
Relates :  
JDK-8326376 - java -version failed with CONF=fastdebug -XX:InitialCodeCacheSize=1024K -XX:ReservedCodeCacheSize=1200k
Relates :  
JDK-8318176 - C2: dont assert in ~GraphKit if compilation had been interrupted
Relates :  
JDK-8318183 - C2: VM may crash after hitting node limit
Description
Analyzing broken bailout chains is onerous. A broken bailout chain occurs when code marks a compilation as failed, but then either that function itself or any of its caller function fails to abort the compilation. That may cause crashes, e.g. JDK-8318183 or JDK-8318445.

It would be helpful if the compilers were to remember details about where in the code the bailout occurred, and in case of a crash, write that info into the crash report.
Comments
Changeset: c90768c9 Author: Thomas Stuefe <stuefe@openjdk.org> Date: 2024-01-08 13:47:43 +0000 URL: https://git.openjdk.org/jdk/commit/c90768c93b26771bb8f4bdbe855d054ad089b337
08-01-2024
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/16247 Date: 2023-10-18 13:32:32 +0000
19-10-2023
Thanks! :)
18-10-2023
[~thartmann] I try to do as the Romans do :-) I saw someone using it for compiler issues. Maybe I'm remembering it. Now I see its also redundant since the sub category is already "compiler." OK, I remove it.
18-10-2023
[~stuefe] Just wondering, what purpose does the 'compiler' label have? We haven't used it in many years and I think the compiler subcomponent is sufficient to mark compiler issues, right?
18-10-2023