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
fix: potential crash on missing render frame #31289
Conversation
71628c4
to
ed8ee5e
Compare
ed8ee5e
to
a4c56ad
Compare
Release Notes Persisted
|
I have automatically backported this PR to "14-x-y", please check out #31333 |
I have automatically backported this PR to "15-x-y", please check out #31334 |
I have automatically backported this PR to "13-x-y", please check out #31335 |
I have automatically backported this PR to "16-x-y", please check out #31336 |
Description of Change
Closes #31281.
Fixes an potential crash in
WebContents::MessageTo
when a render frame has been destroyed. Both other calls toGetRendererApi()
are guarded byCheckRenderFrame()
, and so this PR adds the same check to this third callsite.Checklist
npm test
passesRelease Notes
Notes: Fixes an potential crash in
WebContents::MessageTo
when a render frame has been destroyed.