-
Notifications
You must be signed in to change notification settings - Fork 16.2k
fix: check WebContents before emitting render-process-gone event #27730
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
This should be merged after #27731, which would fix the CI failure. |
8744d05
to
389e3a4
Compare
389e3a4
to
8c6ba88
Compare
Release Notes Persisted
|
I was unable to backport this PR to "10-x-y" cleanly; |
I have automatically backported this PR to "12-x-y", please check out #27756 |
I have automatically backported this PR to "11-x-y", please check out #27757 |
Description of Change
Fix a crash that caused by
render-process-gone
event accessing WebContents after user has destroyed it in thecrashed
event.Checklist
npm test
passesRelease Notes
Notes: Fix crash when destroying WebContents in the
crashed
event.