-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
about the lock when interpreterSample was called #704
Comments
Hi, Thank you for reaching out about this, could you first try with the latest version of 22.3.1? |
hasn't yet; so, If I can get an answer to this phenomenon? So I could confirm the situation, and decide what to do next, upgrade to 22.3.1 or get a way around. |
Another things kept me stay in 22.1, #707; |
what's more ,I found a way around for stack-issue; |
com.oracle.truffle.js.nodes.access.FrequencyBasedPolymorphicAccessNode#interpreterSample
I develop a application using graal.js, with one engine shared among 100+context;
recently I found that sometimes javascript executing thread stuck awhile at
com.oracle.truffle.js.nodes.access.FrequencyBasedPolymorphicAccessNode#interpreterSample
;I guess, it seems like graal.js found it valuable for compiling, and try to generate an sample for compiling,but it locked here;
previously I thought,
org.graalvm.polyglot.Engine
must be shared as large scale as possible, but now it confused me;so I'd like to know the reason why
com.oracle.truffle.js.nodes.access.FrequencyBasedPolymorphicAccessNode#interpreterSample
stucked, and how to avoid it;GraalVM 22.1 with Graal.js 22.1
The text was updated successfully, but these errors were encountered: