On Sun, 6 Nov 2022 23:03:19 GMT, Coleen Phillimore <cole...@openjdk.org> wrote:
>> Coleen has reminded me that I am confused about what the workaround was >> doing - this code doesn't prevent deadlock, it prevents a LinkageError that >> would otherwise occur because the classloader has done something tricky >> (released the monitor) to prevent deadlock. So the correct behaviour here is >> proceed with the class loading and trigger the LinkageError in the other >> thread. > > No, the expectation without this code is a LinkageError: dupicate class > definition. I just started the release-note subtask to describe this. The > expected behavior is that we don't wait, we just let the application load the > class even though they've broken the lock. See release note in progress: https://bugs.openjdk.org/browse/JDK-8296446 ------------- PR: https://git.openjdk.org/jdk/pull/10832
