Node.js[5483]: ../src/node.cc:701:void node::ResetStdio(): Assertion `!(err != 0) || (err == -1 && (*__errno_location ()) == 1)' failed.
Version
18.19.0
Platform
Linux localhost 5.4.0-90-generic #101-Ubuntu SMP Fri Oct 15 20:00:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
No response
What steps will reproduce the bug?
Running nodejs with logging enabled
How often does it reproduce? Is there a required condition?
It reproduces periodically at weird intervals. Doesn't appear to have an actual condition
What is the expected behavior? Why is that the expected behavior?
The expected behavior is that it should be running without issues or at least posting some genuine error. This is expected because this error originates out of a NodeJS core lib, meaning we are dealing with some core error which is usually not expected.
What do you see instead?
Node.js v18.19.0
Node.js[5483]: ../src/node.cc:701:void node::ResetStdio(): Assertion `!(err != 0) || (err == -1 && (*__errno_location ()) == 1)' failed.
1: 0xb95b60 node::Abort() [node]
2: 0xb95bde [node]
3: 0xb4cdd4 [node]
4: 0x7f6332fe58a7 [/lib/x86_64-linux-gnu/libc.so.6]
5: 0x7f6332fe5a60 on_exit [/lib/x86_64-linux-gnu/libc.so.6]
6: 0xad614a node::DefaultProcessExitHandler(node::Environment*, int) [node]
7: 0xb1a3f3 node::Environment::Exit(int) [node]
8: 0xb9909a node::errors::TriggerUncaughtException(v8::Isolate*, v8::Local<v8::Value>, v8::Local<v8::Message>, bool) [node]
9: 0xb997d1 [node]
10: 0xdcd3e0 [node]
11: 0xdce91f v8::internal::Builtin_HandleApiCall(int, unsigned long*, v8::internal::Isolate*) [node]
12: 0x170dfb9 [node]
Additional information
No response