Nicolai ParlogHost
On August 18th, 2026, a mail pops up on the hotspot compiler dev mailing list, and it describes something that is not supposed to happen, a serious new bug in a JDK release candidate phase just a few weeks before general availability.

Apparently, under very specific circumstances, some buffer contents aren't correctly copied and strings can get corrupted.

And so this could be a technical story that dives deep into C2, the part of Hotspot's just-in-time compiler that is tasked with generating the best performing code and that caused the observed misbehavior.

But not only am I not the right person to tell that story, I also think there's another equally interesting one to tell that teaches us a lot about how OpenJDK and the wider Java community collaborates to produce a safe and sound JDK.

That story begins in December 2025 when my colleague Quang Anh Mai files a priority three bug against C2 that has been lurking since JDK 9, a detail we'll come back to.

On December 12th, a pull request for the bug is opened, still in time to potentially make it into JDK 26.

Now, as far as I'm aware, nobody tried to make that happen, but we can learn a lot about the JDK's development process by exploring this hypothetical.

In mid-December 2025, JDK 26 was already branched from the main development line and is in stabilization, which consists of ramp-down phase one and two, followed by release candidate phase.

During all of this, bugs are carefully vetted and labeled as candidates or not, as current or targeted, and maybe as critical.

As you can imagine, and without talking you through the entire process matrix, more important bugs are more likely to get addressed, but the requirements for a bug to be addressed also become stricter as the phases progress, and there's an explicit deferral process for critical bugs that can't be fixed right away.

This triage, defined by JDK Enhancement Proposal 3, exists to direct time and attention towards the most important fixes, while ensuring that less important fixes don't rock the boat on the last stretch towards the release.

So what does all that mean for our C2 bug if someone would've tried to push the fix into JDK 26? In mid-December, 26 is in ramp-down phase one, and our bug is P3, which would make it a candidate.

But it also matters how old it is, and [laughs] remember that this one would be well into elementary school by now, so it'd be merely a targeted bug, the category that is least likely to be fixed.

The weather is nice outside, maybe you take your laptop to the veranda or cafe, and, most importantly, JEP 3 is not curbing your enthusiasm, not even hypothetically.

JDK 26 has been shipped in March, and 27 won't be forked off the main line until early June.

Elastic recently started building against JDK 27's early access builds and now observes a failing test.

It seems like strings get corrupted because some buffer contents aren't correctly copied.

After exploring the issue with others on his team, Lorenzo De Matteis takes to the hotspot compiler dev mailing lists on the 18th.

On August 18th, 2026, a mail pops up on the hotspot compiler dev mailing list, and it describes something that is not supposed to happen, a serious new bug in a JDK release candidate phase just a few weeks before general availability.

Apparently, under very specific circumstances, some buffer contents aren't correctly copied and strings can get corrupted.

And so this could be a technical story that dives deep into C2, the part of Hotspot's just-in-time compiler that is tasked with generating the best performing code and that caused the observed misbehavior.

But not only am I not the right person to tell that story, I also think there's another equally interesting one to tell that teaches us a lot about how OpenJDK and the wider Java community collaborates to produce a safe and sound JDK.

That story begins in December 2025 when my colleague Quang Anh Mai files a priority three bug against C2 that has been lurking since JDK 9, a detail we'll come back to.

On December 12th, a pull request for the bug is opened, still in time to potentially make it into JDK 26.

Now, as far as I'm aware, nobody tried to make that happen, but we can learn a lot about the JDK's development process by exploring this hypothetical.

In mid-December 2025, JDK 26 was already branched from the main development line and is in stabilization, which consists of ramp-down phase one and two, followed by release candidate phase.

During all of this, bugs are carefully vetted and labeled as candidates or not, as current or targeted, and maybe as critical.

As you can imagine, and without talking you through the entire process matrix, more important bugs are more likely to get addressed, but the requirements for a bug to be addressed also become stricter as the phases progress, and there's an explicit deferral process for critical bugs that can't be fixed right away.

This triage, defined by JDK Enhancement Proposal 3, exists to direct time and attention towards the most important fixes, while ensuring that less important fixes don't rock the boat on the last stretch towards the release.

So what does all that mean for our C2 bug if someone would've tried to push the fix into JDK 26? In mid-December, 26 is in ramp-down phase one, and our bug is P3, which would make it a candidate.

But it also matters how old it is, and [laughs] remember that this one would be well into elementary school by now, so it'd be merely a targeted bug, the category that is least likely to be fixed.

The weather is nice outside, maybe you take your laptop to the veranda or cafe, and, most importantly, JEP 3 is not curbing your enthusiasm, not even hypothetically.

JDK 26 has been shipped in March, and 27 won't be forked off the main line until early June.

Elastic recently started building against JDK 27's early access builds and now observes a failing test.

It seems like strings get corrupted because some buffer contents aren't correctly copied.

After exploring the issue with others on his team, Lorenzo De Matteis takes to the hotspot compiler dev mailing lists on the 18th.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.