On 2018-02-26 12:21, Alan Bateman wrote:
http://cr.openjdk.java.net/~redestad/8198492/jdk.00/
This looks okay to me to fix the current issue. There are several
other bugs that look similar and I expect they will go away once you
get this pushed. It might be useful to move JDK-8198492 to the
java.lang.invoke subcomponent, and maybe change the summary so that
it's clearer for anyone looking at in the future.
Thanks!
How about "Bootstrapping java.lang.invoke can cause deadlock after
JDK-8198418"?
/Claes
