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

examples/node folder in ubuntu18.04 error #68

Open
hackgoofer opened this issue Dec 16, 2022 · 1 comment
Open

examples/node folder in ubuntu18.04 error #68

hackgoofer opened this issue Dec 16, 2022 · 1 comment

Comments

@hackgoofer
Copy link

hackgoofer commented Dec 16, 2022

Command ran: npm start after npm install
Device: Azure Kinect DK
This was run on ubuntu18.04

> kinect-azure-demo@1.0.0 start /home/sasha/github/kinect-azure/examples/node
> node .

Kinect Opened


#
# Fatal error in , line 0
# Check failed: result.second.
#
#
#
#FailureMessage Object: 0x7ffe972b4c00
 1: 0xaa8461  [node]
 2: 0x1a471e4 V8_Fatal(char const*, ...) [node]
 3: 0xe9dc49 v8::internal::GlobalBackingStoreRegistry::Register(std::shared_ptr<v8::internal::BackingStore>) [node]
 4: 0xbe7898 v8::ArrayBuffer::GetBackingStore() [node]
 5: 0x9f3c80 napi_get_typedarray_info [node]
 6: 0x7fdacc577b4f Napi::Buffer<unsigned char>::New(napi_env__*, unsigned char*, unsigned long) [/home/sasha/github/kinect-azure/lib/binding/napi-v4/kinectAzure.node]
 7: 0x7fdacc57212e  [/home/sasha/github/kinect-azure/lib/binding/napi-v4/kinectAzure.node]
 8: 0x7fdacc57618b Napi::ThreadSafeFunction::CallJS(napi_env__*, napi_value__*, void*, void*) [/home/sasha/github/kinect-azure/lib/binding/napi-v4/kinectAzure.node]
 9: 0xa06420  [node]
10: 0x13c0d06  [node]
11: 0x13d3274  [node]
12: 0x13c1658 uv_run [node]
13: 0xa7b782 node::NodeMainInstance::Run() [node]
14: 0xa03945 node::Start(int, char**) [node]
15: 0x7fdace7a1c87 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
16: 0x98c58c  [node]
@hackgoofer hackgoofer changed the title Tried running the examples/node folder examples/node folder in ubuntu18.04 error Dec 16, 2022
@hackgoofer
Copy link
Author

oh I fixed it by upgrading node to >= 17

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

1 participant