Fabio Niephaus

@imgoby could you please try with Oracle GraalVM for JDK 17 (`sdk install java 17.0.10-graal`), or CE? Maybe this issue was already fixed in that release.

Hi @JiriOndrusek, thanks for the ticket. Could you try running this on a newer GraalVM? 22.3.2 is a bit old, maybe we fixed this in the meantime. The latest GraalVM...

Thanks for raising this, @tomasbjerre. Sure, we could extend the error message as you suggested. It would still be interesting to know if this is caused by normal end-user code...

> I am new to Graalvm, I don't know what SVM internals are. I would suggest you include enough information in the error in order to determine that. Ok, good...

#8400 is already in the merge queue. You'll need to build from source though if you want to test it today, or wait a few days for a dev build.

Thanks for the ticket, @SergejIsbrecht. This design decision is relatively old and we are considering changing the behavior. Please allow some time for this though as it requires significantly more...

I think you should be able to achieve something like this using a [`statementLimit`](https://www.graalvm.org/sdk/javadoc/org/graalvm/polyglot/ResourceLimits.Builder.html#statementLimit-long-java.util.function.Predicate-), which is [one of many supported resource limits](https://www.graalvm.org/latest/security-guide/polyglot-sandbox/#resource-limits). I'm not entirely sure how statements are counted...

Maybe this is something @roberttoyonaga likes to look into?

> I'm happy to look into this eventually, if nobody else picks this up Cool, thanks! > However, it probably wont be on my to-do list for some time. Typo?...

Thanks for the PR, @zakkak. Aren't you documenting more of a bug or do you actually make use of this? Registering everything for build-time initialization seems rather dangerous.