-
Notifications
You must be signed in to change notification settings - Fork 16.3k
fix: launch crash when null device is disabled on Windows #47870
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
base: main
Are you sure you want to change the base?
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.
LGTM, thanks!
@zuohuiyang could you please rebase this? You'll also need to sign your commit before it can be merged. |
ce779e3
to
ec5de79
Compare
add node flag node::ProcessInitializationFlags::kNoStdioInitialization Co-authored-by: yangliu <yangliu.leo@bytedance.com>
ec5de79
to
d5ef01b
Compare
@codebytere Okay, I've rebased and signed my commit. |
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.
API LGTM
add node flag node::ProcessInitializationFlags::kNoStdioInitialization
Description of Change
This PR continues #44882 (originally by @yangllu, my colleague).
I've taken over this task and addressed all 4 review comments:
All 3 were updated exactly as suggested (@deepak1556).
For parameter passing, I didn’t just send it to the Renderer. Since the node module is also used in the Utility process, I added it there as well."
Checklist
npm test
passesRelease Notes
Notes: add support for
--no-stdio-init
to be used when nul device is disabled on windows