-
Notifications
You must be signed in to change notification settings - Fork 29.1k
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
Deadlock at process shutdown #54918
Comments
As written in #52550 (comment), applying the patch from #47452 seems to fix the issue, but it is not a solution since that patch brings other issues. |
This can been seen in various CI runs, assuming confirmed-bug |
The output of
|
@aduh95 see #54918 (comment). It seems the same patch. |
No it's not, it's based on it but it's meant to fix the test failures. |
The issue persists 😞
Also,
|
Version
v23.0.0-pre
Platform
Subsystem
No response
What steps will reproduce the bug?
There is a deadlock that prevents the Node.js process from exiting. The issue is causing a lot (all?) of timeout failures in our CI. It can be reproduced by running a test in parallel with our
test.py
tool, for exampleSee also
test-stream-readable-unpipe-resume
#54133 (comment)test-net-write-fully-async-buffer
as flaky #52959 (comment)How often does it reproduce? Is there a required condition?
Rarely, but often enough to be a serious issue for CI.
What is the expected behavior? Why is that the expected behavior?
The process exits.
What do you see instead?
The process does not exit.
Additional information
Attaching
gdb
to two of the hanging processes obtained from the command above, produces the following outputs:The text was updated successfully, but these errors were encountered: