-
Notifications
You must be signed in to change notification settings - Fork 16.2k
fix: libuv hang on Windows #28175
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
fix: libuv hang on Windows #28175
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there any way we can test for this?
@MarshallOfSound i'll see what i can do 🤔 |
c640620
to
d7327d0
Compare
d7327d0
to
c1377e8
Compare
Asan test failures are unrelated - merging. |
Release Notes Persisted
|
I have automatically backported this PR to "13-x-y", please check out #28335 |
I was unable to backport this PR to "10-x-y" cleanly; |
I have automatically backported this PR to "11-x-y", please check out #28336 |
I have automatically backported this PR to "12-x-y", please check out #28337 |
Description of Change
Closes #28154.
#25869 used
uv_loop_->iocp
to decide whether to re-prep the message loop, and it turns out not to be the case that it works and updates the same way thatuv_backend_fd
does, so what resulted was that whenallowRendererProcessReuse
was true the loop would not re-prep on reload and libuv would hang.This fixes that by only handling this case on non-Windows systems.
Tested with https://gist.github.com/codebytere/2face1c26d09e38c06f49111c3fca13f.
Checklist
npm test
passesRelease Notes
Notes: Fixed an issue where some Node.js modules would hang on page reload on Windows.