-
Notifications
You must be signed in to change notification settings - Fork 29.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node.js[5483]: ../src/node.cc:701:void node::ResetStdio(): Assertion `!(err != 0) || (err == -1 && (*__errno_location ()) == 1)' failed. #51519
Comments
Can you provide a minimal repro? // 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); |
Without a reproducible snippet of code, it seems very hard to me to find out what is causing this |
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. |
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. |
(The stalled bot doesn't appear to be working, so I've manually closed. Feel free to reopen if this is no longer stalled) |
I just experienced this:
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 For the last hour-plus before it fails, this script has done nothing but orchestrate a series I've restarted it with much less output to stdout and will report on whether that seems to matter at all. |
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. |
If you can provide a minimal reproduction, it'd be easier for someone to reproduce. |
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. |
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?
Additional information
No response
The text was updated successfully, but these errors were encountered: