Skip to content
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

Open
tellmewhattodo opened this issue Feb 22, 2023 · 4 comments
Open

about the lock when interpreterSample was called #704

tellmewhattodo opened this issue Feb 22, 2023 · 4 comments
Assignees

Comments

@tellmewhattodo
Copy link

tellmewhattodo commented Feb 22, 2023

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

@oubidar-Abderrahim oubidar-Abderrahim self-assigned this Feb 27, 2023
@oubidar-Abderrahim
Copy link
Member

Hi, Thank you for reaching out about this, could you first try with the latest version of 22.3.1?

@tellmewhattodo
Copy link
Author

Hi, Thank you for reaching out about this, could you first try with the latest version of 22.3.1?

hasn't yet;
it's pretty difficult for me to try this;
cause I couldn't reproduce it in my local, and reproduce in production is rather risky;

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.

@tellmewhattodo
Copy link
Author

Another things kept me stay in 22.1, #707;
upgrading is currently un acceptable

@woess woess self-assigned this Feb 28, 2023
@tellmewhattodo
Copy link
Author

what's more ,I found a way around for stack-issue;
so, is there any change about this issue between 22.1 and 22.3.1 ?

@oubidar-Abderrahim oubidar-Abderrahim removed their assignment Mar 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants