fix: crash when using vm after window.open()
#37506
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Change
Closes #37404.
Refs #32057.
Fixes a potential crash when using the
vm
module in the renderer process after callingwindow.open('')
. This started happening after nodejs/node#44252, which we rolled into Electron via 75d2caf. It appears that eagerly loading the Node.js environment when opening a child window with a blank url also requires a delay, otherwise Node.js isn't able to properly set up thev8::Context
for use with vm.Checklist
npm test
passesRelease Notes
Notes: Fixed a potential crash when using the
vm
module in the renderer process after callingwindow.open('')
.