Open arasmussen opened 5 months ago
Just migrated our instances to Graviton2 (from m7g to m6g) and confirmed we are not able to reproduce this issue there.
Coredump backtrace:
(gdb) bt
#0 0x0000000000d61274 in v8::Object::Set(v8::Local<v8::Context>, v8::Local<v8::Value>, v8::Local<v8::Value>) ()
#1 0x0000000000c4df44 [PAC] in node::(anonymous namespace)::ProcessWrap::Spawn(v8::FunctionCallbackInfo<v8::Value> const&) ()
#2 0x0000000000dab0e0 [PAC] in 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)
()
#3 0x0000000000dac208 [PAC] in v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) ()
#4 0x000000000168000c [PAC] in Builtins_CEntry_Return1_DontSaveFPRegs_ArgvOnStack_BuiltinExit ()
#5 0x005600000168000c in ?? ()
I have tried downgrading to pm2 5.3.1 and 5.1.1 and ran into the same issue.
I also tried downgrading to node 18.12.1. Upgrading to node 20 appears to fix.
What's going wrong?
/var/log/messages
)How could we reproduce this issue?
pm2 startOrReload
) result in a crash/coredump.Supporting information