-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
fatal v8 error:Entering the V8 API without proper locking in place #23997
Comments
I know Android is currently an unsupported platform, but any chance someone wants to comment on this issue? @nodejs/v8 |
Don't use lockers if you only use a single thread. I can't provide any more advice without more context unfortunately. |
@JaneaSystems have a working Android version (@joaocgreis, @bzoz) |
Thanks @hashseed . It may be solved without using a locker. |
Regarding https://github.com/janeasystems/nodejs-mobile on Android: We don't have any related issue, nor have anything similar happened on out tests, so I'm not sure what this can be. Our scenario is single threaded use for mobile, so it may not even occur inside that scenario, since we're not using the mentioned |
@lolobug This sounds like an issue with embedding Node and using |
I'm going to close this, but feel free to re-open if code is shared from original poster or if it otherwise becomes possible to troubleshoot further. |
Subsystem:
V8 fatat handler message : Entering the V8 API without proper locking in place (HandleScope::HandleScope)
This occurs by chance.
I noticed :
uv_check_start(immediate_check_handle(), CheckImmediate);
Actually I place all the operations of node in a single thread and use a V8::Locker.
Is it possible that the CheckImmediate will switch to another thread?
there's V8 HandleScope::Initialize code:
The text was updated successfully, but these errors were encountered: