We've had a number of reports of LinkageError-related problems with a
constructor handle acquired through publicLookup.

Here's the commit that fixed the problem, with a link to a PR explaining
the error:


It seems like the error indicates a class is getting loaded into the
bootstrap classloader during lookup when it should not, and as a result any
child classloaders that load it later on have a conflicting copy.

Thoughts? This is tested on a very recent Java 8.

- Charlie
mlvm-dev mailing list

Reply via email to