On Tue, 8 Sep 2026 14:20:27 GMT, Dan Heidinga <[email protected]> wrote:
> Another option here is to simply drop the reference from the > classloader->class as a consequence of removing the ArrayList. For 20+ years, a heap walk that visits a class loader will visit the classes that it has defined. It would be a significant change to not do this. So I think we have to be cautious, moves in that direction would require some advanced notice and or a XX option to allow existing agents to continue to work. (I think we need to look at this in the context of more long term deprecating/removal of JVMTI features beyond the core required to support debugging. Many aspects of JVMTI, esp. profiling, have been surpassed by other features. JVMTI is very invasive and interacts with man new features. The heap functions are good candidates to re-examine as to their usefulness in 2026.) ------------- PR Comment: https://git.openjdk.org/jdk/pull/32519#issuecomment-5587273542
