GraalVM reuses the normal java class loading logic which is platform-dependent. So e.g. on windows it will load some windows-specific File subclasses and the like, so this is more of an architectural problem to a certain degree.
(It really does loadClass everything reachable based on the code to be compiled)
(It really does loadClass everything reachable based on the code to be compiled)