JDK-8357175 : Failure to generate or load AOT code should be handled gracefully
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 25
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2025-05-16
  • Updated: 2025-06-01
  • Resolved: 2025-06-01
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 25
25 masterFixed
Description
Only under special AOT flag or in debug VM failure to generate or load AOT code should cause VM exit with message or hit assert/fatal.
By default the failed AOT code should be discarded with UL message about it by request (log_info) and VM and AOT process should continue run. Or stop AOT code processing (for exampale, when no reserved memory for AOT code left).
Unless we hit some catastrophic failure: OOM fro example. This is similar how JIT compilers behave.
Comments
Changeset: e3eb089d Branch: master Author: Vladimir Kozlov <kvn@openjdk.org> Date: 2025-06-01 03:57:28 +0000 URL: https://git.openjdk.org/jdk/commit/e3eb089d47d62ae6feeba3dc6b3752a025e27bed
01-06-2025
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jdk/pull/25525 Date: 2025-05-29 18:45:11 +0000
29-05-2025