> 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 with a new target base due to a merge or a rebase. The pull request now contains 10 commits: - Merge branch 'master' into loader - Add another test to show change of behavior - Self review. - Self review. - Fix assert. - Add a test to show that the class is still found in hprof even though classes is not in ClassLoader. - Make an assert to check that stale classes aren't in loader constraint table, now that addClass() isn't called so no OOM possible. - Fix comments. - Fix copyrights. - 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=08 Stats: 393 lines in 10 files changed: 336 ins; 43 del; 14 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
