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). ------------- Commit messages: - 8391308: Remove ClassLoader.classes vector and addClass call Changes: https://git.openjdk.org/jdk/pull/32519/files Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=32519&range=00 Issue: https://bugs.openjdk.org/browse/JDK-8391308 Stats: 41 lines in 6 files changed: 0 ins; 37 del; 4 mod Patch: https://git.openjdk.org/jdk/pull/32519.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/32519/head:pull/32519 PR: https://git.openjdk.org/jdk/pull/32519
