fix: crash when RenderFrameHost is nullptr #34410
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
VerteDinde
requested changes
Jun 1, 2022
VerteDinde
approved these changes
Jun 1, 2022
MarshallOfSound
approved these changes
Jun 1, 2022
|
/trop run backport-to main |
|
This PR has not been merged yet, and cannot be backported. |
|
Replaced by #34411 for CI reasons |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Follow up to #33919. A code path involving speculative RenderFrameHosts being created is resulting in a crash when initially setting up the Mojo connection.
More investigation is still needed to determine what leads to this state where
render_frame_is a nullptr.Checklist
npm testpassesRelease Notes
Notes: Fixed potential crash in WebFrameMain when performing a cross-origin navigation.