fix: crash on window.close()
with webContents
on blur
#47933
Merged
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 #47830.
it's possible that
inspectable_web_contents_
is null in some cases. In the above bug, the WebContentsView's webContents callswindow.close()
, which causes the "blur" event to be emitted onwebContents
. When the user handles the event in the callback,inspectable_web_contents_
can already be gone, aswindow.close()
causes asynchronous destruction.Checklist
npm test
passesRelease Notes
Notes: Fixed a crash when calling some
webContents
functions afterwindow.close()
.