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

FATAL ERROR: HandleScope::HandleScope Entering the V8 API without proper locking in place #1686

Closed
yashykt opened this issue Feb 8, 2021 · 1 comment

Comments

@yashykt
Copy link
Member

yashykt commented Feb 8, 2021

Copied from grpc/grpc#25359

What version of gRPC and what language are you using?
grpc from npm 1.24.4
node 12.18.2 (and same issue in v14)

What operating system (Linux, Windows,...) and version?
Linux 5.8.0-41-generic #46~20.04.1-Ubuntu SMP Mon Jan 18 17:52:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

What runtime / compiler are you using (e.g. python version or version of gcc)
the one that npm provides

What did you do?
trying to launch my app using worker_threads - via thread.js - see also andywer/threads.js#334

What did you expect to see?
a working app

What did you see instead?
node crash

FATAL ERROR: HandleScope::HandleScope Entering the V8 API without proper locking in place
 1: 0xa0bb60 node::Abort() [/home/cameronbraid/.nvm/versions/node/v12.18.2/bin/node]
 2: 0xa0bf6c node::OnFatalError(char const*, char const*) [/home/cameronbraid/.nvm/versions/node/v12.18.2/bin/node]
 3: 0xb81eca v8::Utils::ReportApiFailure(char const*, char const*) [/home/cameronbraid/.nvm/versions/node/v12.18.2/bin/node]
 4: 0xb8346e v8::HandleScope::HandleScope(v8::Isolate*) [/home/cameronbraid/.nvm/versions/node/v12.18.2/bin/node]
 5: 0x97a9ee node::InternalCallbackScope::InternalCallbackScope(node::Environment*, v8::Local<v8::Object>, node::async_context const&, int) [/home/cameronbraid/.nvm/versions/node/v12.18.2/bin/node]
 6: 0x97c065 node::MakeCallback(v8::Isolate*, v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*, node::async_context) [/home/cameronbraid/.nvm/versions/node/v12.18.2/bin/node]
 7: 0x7f3b2c404913  [/media/workspace/drivenow-frontend/node_modules/grpc/src/node/extension_binary/node-v72-linux-x64-glibc/grpc_node.node]
 8: 0x7f3b2c40f283  [/media/workspace/drivenow-frontend/node_modules/grpc/src/node/extension_binary/node-v72-linux-x64-glibc/grpc_node.node]
 9: 0x133b24c  [/home/cameronbraid/.nvm/versions/node/v12.18.2/bin/node]
10: 0x1333dd8 uv_run [/home/cameronbraid/.nvm/versions/node/v12.18.2/bin/node]
11: 0xa4ecf5 node::NodeMainInstance::Run() [/home/cameronbraid/.nvm/versions/node/v12.18.2/bin/node]
12: 0x9dcc68 node::Start(int, char**) [/home/cameronbraid/.nvm/versions/node/v12.18.2/bin/node]
13: 0x7f3b2feeb0b3 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
14: 0x979215  [/home/cameronbraid/.nvm/versions/node/v12.18.2/bin/node]

@cameronbraid

@murgatroid99
Copy link
Member

This is a known issue, see #778. I suggest switching to @grpc/grpc-js, both to avoid this specific problem, and because the grpc package will be deprecated soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants