-
Notifications
You must be signed in to change notification settings - Fork 16.2k
fix: crash on browserView.webContents.destroy() #31794
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
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.
Change makes sense to me but I'd like a third opinion too; this feels like I might be missing some nuance.
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.
This approach makes sense to me 👍
Release Notes Persisted
|
I have automatically backported this PR to "14-x-y", please check out #31825 |
I have automatically backported this PR to "15-x-y", please check out #31826 |
I have automatically backported this PR to "16-x-y", please check out #31827 |
Description of Change
Fixes an issue where
BrowserView
s crashed ifview.webContents.destroy()
is called after loading a URL. This happened because when the webContents closed synchronously, theInspectableWebContents
was forced to close before all observers had been notified, causing a CHECK here.To fix this, I chose to remove the
BrowserView
type from the synchronous conditions, though if there is a preferred approach I'm happy to modify this.Checklist
npm test
passesRelease Notes
Notes: Fixes an issue where
BrowserView
s crashed ifview.webContents.destroy()
is called after loading a URL.