ProcessInitializationFlags::Flags Assertion `(err) == (0)'

[ericfortis]

Version

v20.10.0

Platform

FreeBSD 14.0-RELEASE-p5 FreeBSD 14.0-RELEASE-p5 #0: Tue Feb 13 23:37:36 UTC 2024 root@amd64-builder.daemonology.net:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64

Subsystem

No response

What steps will reproduce the bug?

In FreeBSD using this rc script node crashes.

But it works fine if I manually service node start

How often does it reproduce? Is there a required condition?

Always and only at boot time

What is the expected behavior? Why is that the expected behavior?

No response

What do you see instead?

/usr/local/bin/node[49112]: ../src/node.cc:538:void node::PlatformInit(ProcessInitializationFlags::Flags): Assertion `(err) == (0)' failed.
/usr/local/bin/node[49327]: ../src/node.cc:538:void node::PlatformInit(ProcessInitializationFlags::Flags): Assertion `(err) == (0)' failed.
 1: 0x1760de0 node::Abort() [/usr/local/bin/node]
 1: 0x1760de0 node::Abort() [/usr/local/bin/node]
 2: 0x1760b0b node::Assert(node::AssertionInfo const&) [/usr/local/bin/node]
 3: 0x171eb01 node::InitializeOncePerProcess(std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >> > const&, node::ProcessInitializationFlags::Flags) [/usr/local/bin/node]
 4: 0x171f1ea node::Start(int, char**) [/usr/local/bin/node]
 5: 0x82fcefafa __libc_start1 [/lib/libc.so.7]
 2: 0x1760b0b node::Assert(node::AssertionInfo const&) [/usr/local/bin/node]
 3: 0x171eb01 node::InitializeOncePerProcess(std::__1::vector<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >, std::__1::allocator<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >> > const&, node::ProcessInitializationFlags::Flags) [/usr/local/bin/node]
 4: 0x171f1ea node::Start(int, char**) [/usr/local/bin/node]
 5: 0x82e8d1afa __libc_start1 [/lib/libc.so.7]

Additional information

No response