Uploaded October 2026 | Updated November 2026, 3 days ago
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. This is bad, very bad even, and obviously requires analysis and a fix. This is the story of the structure and community that fixes bugs like these and how they operate. We also take a quick look at JavaOne, the Inside Java Podcast, and JDK 28, which is shaping up to be a big release.
~~~~~ Chapters ~~~~~
0:00 Intro
0:18 A Critical Bug
JEP 3: openjdk.org/jeps/3
the original issue: bugs.openjdk.org/browse/JDK-8373591
the original PR: github.com/openjdk/jdk/pull/28789
Lorenzo's bug description: mail.openjdk.org/archives/list/hotspot-compiler-dev@openjdk.org/thread/5NVKBE3C5T5ULKVO5T3RTUQZDIXQMHBE
Chris' alarm for the P1 bug: mail.openjdk.org/archives/list/jdk-dev@openjdk.org/thread/EPJNIMIAROC2QELIZE5MAGU4D6S3FEVG/#K52LJL4HZJE565UBU465PT4ZBRC2XV4Y
the bug in JDK 27: bugs.openjdk.org/browse/JDK-8390546
backing out the change on the mail branch: bugs.openjdk.org/browse/JDK-8390590
backporting the backout to JDK 27: bugs.openjdk.org/browse/JDK-8390663
Mark's confirmation: mail.openjdk.org/archives/list/jdk-dev@openjdk.org/message/K52LJL4HZJE565UBU465PT4ZBRC2XV4Y
redoing the change on the main branch: bugs.openjdk.org/browse/JDK-8390617
Quality Outreach: wiki.openjdk.org/spaces/quality/pages/18448461/Quality+Outreach
6:18 Meat Space
JavaOne: javaone.com
Inside Java Podcast: https://inside.java/podcast/
7:12 JDK 28
early-access builds: https://inside.java/podcast/
feature list: openjdk.org/projects/jdk/28
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. This is bad, very bad even, and obviously requires analysis and a fix. This is the story of the structure and community that fixes bugs like these and how they operate. We also take a quick look at JavaOne, the Inside Java Podcast, and JDK 28, which is shaping up to be a big release.
~~~~~ Chapters ~~~~~
0:00 Intro
0:18 A Critical Bug
JEP 3: openjdk.org/jeps/3
the original issue: bugs.openjdk.org/browse/JDK-8373591
the original PR: github.com/openjdk/jdk/pull/28789
Lorenzo's bug description: mail.openjdk.org/archives/list/hotspot-compiler-dev@openjdk.org/thread/5NVKBE3C5T5ULKVO5T3RTUQZDIXQMHBE
Chris' alarm for the P1 bug: mail.openjdk.org/archives/list/jdk-dev@openjdk.org/thread/EPJNIMIAROC2QELIZE5MAGU4D6S3FEVG/#K52LJL4HZJE565UBU465PT4ZBRC2XV4Y
the bug in JDK 27: bugs.openjdk.org/browse/JDK-8390546
backing out the change on the mail branch: bugs.openjdk.org/browse/JDK-8390590
backporting the backout to JDK 27: bugs.openjdk.org/browse/JDK-8390663
Mark's confirmation: mail.openjdk.org/archives/list/jdk-dev@openjdk.org/message/K52LJL4HZJE565UBU465PT4ZBRC2XV4Y
redoing the change on the main branch: bugs.openjdk.org/browse/JDK-8390617
Quality Outreach: wiki.openjdk.org/spaces/quality/pages/18448461/Quality+Outreach
6:18 Meat Space
JavaOne: javaone.com
Inside Java Podcast: https://inside.java/podcast/
7:12 JDK 28
early-access builds: https://inside.java/podcast/
feature list: openjdk.org/projects/jdk/28








![Principles of Memory Management in Java
Java programs use garbage collection, and the JDK offers several collectors with different characteristics. But they also share important design choices that distinguish them from garbage collectors in other languages—choices every Java developer should understand.
In this talk, we’ll explore why the JDK’s garbage collectors work the way they do and how Java memory management affects application performance. We’ll look at the sometimes non-obvious relationship between RAM and CPU, and why they must always be considered together.
Finally, we’ll ask: is Java wasteful because it uses too much memory—or are other languages wasteful because they use too little?
Presented by Ron Pressler (Oracle) at JavaOne 2026 (CA, March 2026).
All https://www.youtube.com/playlist?list=PLX8CzqL3ArzUMVSzm-z if8BIB55EGl4 talks.
• ISMM25 Keynote: Industry GC Insights from OpenJDK ⇒ https://www.youtube.com/watch?v=mLNFVNXbw7I
• Java *is* Memory Efficient [AtA] Inside Java Podcast ⇒ https://youtu.be/M_HCG1JPMQE?si=SHy-sYPEJXkL8RIn
Tags: #Java #GC #JavaOne #JVM
LRN1449 17 AUDI Principles of Memory Management in Java](https://i.ytimg.com/vi/xr73mR7ii9M/mqdefault.jpg)

