On Thu, 27 Aug 2026 22:50:13 GMT, Coleen Phillimore <[email protected]> wrote:
>> Remove the upcall to addClass during class loading. The comment says it's >> only so GC can keep classes alive while the class loader is alive. We have >> other ways to do that. There were some JVMTI tests in the past that failed >> without this vector but today seems to be only one test. Maybe there's some >> code that has a dependency on this in heap walking. >> Tested tier1-6 >> >> --------- >> - [x] I confirm that I make this contribution in accordance with the >> [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). > > Coleen Phillimore has updated the pull request incrementally with one > additional commit since the last revision: > > Fix copyrights. @coleenp Would it be possible to provide a summary on the how this changes HRPOF heap dumps and JVMTI heap walking tools? I'm wondering about tools that use functions like FollowReferences to follow refs. If a ClassLoader object is encountered today then it will follow the refs to all classes defined by that class loader. With the change then it won't do that, is that right? I'm wondering if the refs will need to be synthesized to avoid breakage. ------------- PR Comment: https://git.openjdk.org/jdk/pull/32519#issuecomment-5450252834
