Node.js[5483]: ../src/node.cc:701:void node::ResetStdio(): Assertion `!(err != 0) || (err == -1 && (*__errno_location ()) == 1)' failed.

[TheRealRaeed]

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

[marco-ippolito]

Can you provide a minimal repro?
This is the assertion that fails

      // Normally we expect err == 0. But if macOS App Sandbox is enabled,
      // tcsetattr will fail with err == -1 and errno == EPERM.
      CHECK_IMPLIES(err != 0, err == -1 && errno == EPERM);

[TheRealRaeed]

Try making a simple express app and running it in linux using this command

Then do some other simple linux commands and then log off the server using exit you will notice (if it happens) that it will go down, sometimes it takes a few days or hours, but if you visit the express site throughout the day, and use the linux server too, eventually this error comes up and you will notice the app has crashed.

[marco-ippolito]

Without a reproducible snippet of code, it seems very hard to me to find out what is causing this

[github-actions]

This issue/PR was marked as stalled, it will be automatically closed in 30 days. If it should remain open, please leave a comment explaining why it should remain open.

[RedYetiDev]

Hi! I've marked this issue as stalled, as @marco-ippolito asked for a minimal reproduction back in January, and one is yet to be provided.

[RedYetiDev]

(The stalled bot doesn't appear to be working, so I've manually closed. Feel free to reopen if this is no longer stalled)

[boutell]

I just experienced this:

Node.js[843246]: ../src/node.cc:701:void node::ResetStdio(): Assertion `!(err != 0) || (err == -1 && (*__errno_location ()) == 1)' failed.

node --version
v18.20.4

My script is running for a long period of time (hours) and producing a lot of output on stdout and a small amount on stderr. It is not reading anything from stdin.

I don't really know how to get from here to a minimal repro because I have tons of nodejs scripts, and no others have ever done this. My script spends a lot of time in child_process.execSync calls, I don't know if that could be relevant or if it's entirely irrelevant (e.g. perhaps this part of src/node.cc is concerned entirely with the stdout of the main process itself, which is not involved, since I'm not passing interesting options like stdio: 'inherit').

For the last hour-plus before it fails, this script has done nothing but orchestrate a series cp.execSync calls to the AWS CLI, with no fancy options beyond { encoding: 'utf8' }. I do pay attention to the return value and parse it as JSON on each call. I can't see anything that would cause memory pressure because it works in small batches and retains nothing between batches. Stdout and stderr are both being piped to a file (at the bash shell level).

I've restarted it with much less output to stdout and will report on whether that seems to matter at all.

[boutell]

Unfortunately this happens consistently even with much less output.

I'm going to try zero output just to see if it really has anything to do with normal use of standard output at all.

I neglected to mention I'm running Ubuntu 22.04 LTS.

[RedYetiDev]

If you can provide a minimal reproduction, it'd be easier for someone to reproduce.

[boutell]

I realize that. The difficulty is that it's probably dependent on specific responses I'm getting from an external service (AWS) and they contain information that isn't mine to share. But if I can nail it down and it's not something sensitive I will share it.