On 23/04/2019 15:47, Sciampacone, Ryan wrote:
- The problem doesn't exist at jdk9+ because the classes causing this problem get loaded and
initialized as part of the initialization sequence "naturally" (ie: I see no indication
that they are loaded to solve this specific problem). I agree that jdk8 is unlikely to have
dramatic changes in initialization moving forward, but putting it as part of (to me) the more
streamlined create_vm() function made sense from a "safety" perspective as it felt more
controlled and unlikely to be perturbed by any other change in the initialization code flow (class
library or vm).
True for JDK 9 but there has been significant changes since than and the
file system is not eagerly loaded since JDK 10 or 11. So I think it
needs further investigation to see if we have a potential issue in the
main line or not.
-Alan
