> 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 two additional commits since the last revision: - fix copyright - This is why I picked JVMTI_HEAP_REFERENCE_ARRAY_ELEMENT. It's what it used to return. ------------- Changes: - all: https://git.openjdk.org/jdk/pull/32519/files - new: https://git.openjdk.org/jdk/pull/32519/files/473a1f2c..f76b4293 Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=32519&range=11 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=32519&range=10-11 Stats: 12 lines in 2 files changed: 10 ins; 0 del; 2 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
