Illegal Hardware Exception

[AndrewJSchoen]

Hi all,

I have been using this bridge more frequently, since it was actually able to translate visualization messages for the ros3djs library to use. However, I have been encountering a frequent issue in which the node randomly dies. Running in debug mode, here is the output:

#
# Fatal error in , line 0
# Check failed: result.second.
#
#
#
#FailureMessage Object: 0x7ffeefbe7bf0
 1: 0x1000df830 node::NodePlatform::GetStackTracePrinter()::$_3::__invoke() [/usr/local/bin/node]
 2: 0x100a49dc1 V8_Fatal(char const*, ...) [/usr/local/bin/node]
 3: 0x10038ef38 v8::internal::GlobalBackingStoreRegistry::Register(std::__1::shared_ptr<v8::internal::BackingStore>) [/usr/local/bin/node]
 4: 0x100199f1b v8::ArrayBuffer::GetBackingStore() [/usr/local/bin/node]
 5: 0x10006e143 void node::Buffer::(anonymous namespace)::StringWrite<(node::encoding)1>(v8::FunctionCallbackInfo<v8::Value> const&) [/usr/local/bin/node]
 6: 0x1001db744 v8::internal::FunctionCallbackArguments::Call(v8::internal::CallHandlerInfo) [/usr/local/bin/node]
 7: 0x1001dadce v8::internal::MaybeHandle<v8::internal::Object> v8::internal::(anonymous namespace)::HandleApiCallHelper<false>(v8::internal::Isolate*, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::HeapObject>, v8::internal::Handle<v8::internal::FunctionTemplateInfo>, v8::internal::Handle<v8::internal::Object>, v8::internal::BuiltinArguments) [/usr/local/bin/node]
 8: 0x1001da5f2 v8::internal::Builtin_Impl_HandleApiCall(v8::internal::BuiltinArguments, v8::internal::Isolate*) [/usr/local/bin/node]
 9: 0x10077d739 Builtins_CEntry_Return1_DontSaveFPRegs_ArgvOnStack_BuiltinExit [/usr/local/bin/node]
10: 0x100715f82 Builtins_InterpreterEntryTrampoline [/usr/local/bin/node]
[1]    10431 illegal hardware instruction  DEBUG=ros2-web-bridge* node bin/rosbridge.js

It isn't super clear from this what is happening. Any thoughts?

[minggangw]

From the backtrack you offered, I guess the the nodejs > 13.0.0, and if so, please use v12.21.0 instead. It's a known issue on the latest stable nodejs release.