fix: crash when switching origins with emulation settings set #35466
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 #35389.
When we force change origins, our debugger class (a subclass of
content::DevToolsAgentHostClient
) isn't aware of those changes unless we hookRenderFrameHostChanged
. If we don't do this, some navigation lifecycle events {loadingFinished, dataReceived} emitted by the renderer are lost. We disconnect and reconnect the webcontents to theDevToolsAgentHost
to prevent this from happening.As of CL:3758294. this results in a DCHECK, since
DevToolsAgentHost::DisconnectWebContents
results in a call toUpdateDeviceEmulationState
andhost_
is nullptr. To fix this, we revert those state update calls to early returns.Upstreamed at CL:3856525
Checklist
npm test
passesRelease Notes
Notes: Fixed a crash when switching origins with emulation settings set.