Open kohlschuetter opened 8 months ago
Thanks for the excellent bug report!
I assume that GraalVM-Espresso refers to the standalone builds listed here. The Espresso standalone is a legacy GraalVM, the issue is not caused by Espresso but from this legacy (before Truffle Unchained) distribution. Running on HotSpot e.g. $ESPRESSO_STANDALONE/bin/java -server ...
fails in the same way.
As a workaround you can run with -Dgraalvm.locatorDisabled=true
. I tested your snippet and it works fine.
I would advice against running other Truffle languages within Espresso, because these inner languages will run in interpreted mode only. Ideally, you'd embed Espresso as a sibling to other languages within the same polyglot context.
Describe GraalVM and your environment :
java -Xinternalversion
: (java -Xinternalversion
shows help only; output fromjava -version
instead:)Have you verified this issue still happens when using the latest snapshot? Yes.
Describe the issue
I'm using the following Maven dependencies in my library project to use GraalJS so I can execute some JavaScript code.
The code is supposed to be compatible with all Java VMs version 17 and above.
It all works fine on regular Hotspot-based VMs, apart from a separate issue on OpenJ9 (tracked in https://github.com/oracle/graal/issues/7679). However, when running on an Espresso JVM, the following exception is thrown when launching the code:
Code snippet or code repository that reproduces the issue
Steps to reproduce the issue
Expected behavior The code should execute in all three environments.
Additional context Add any other context about the problem here. Specially important are stack traces or log output. Feel free to link to gists or to screenshots if necesary