Closed cyberpwnn closed 3 years ago
That is quite the dark side of manifold. What JDK version are you building with?
Nm I see 16.0.2
The is a tricky one. My guess is the Java build process is a recycled one, or perhaps some other set of actions involving the JRE were executed on the process before the build commenced. Not that this situation is not supported, but if code prior to the NecessaryEvilUtil initialization happens to exercise the exact same Java internals manifold is trying to hack, I suppose it is possible that the state of the VM, in particular the Module class metadata, becomes invariant where manifold can't change it via Unsafe.
This is just a guess, but if this is indeed what is happening, you can prevent it by building from a fresh JVM, perhaps by killing any existing reusable ones from the build environment. That, or simply try building again.
Wish I had a better, more definitive answer for you.
Any idea what could be causing this? It doesnt happen 100% of the time and only happens when building via gh actions