tree 349f9527af6a753075fe2d55b66f262838339e87
parent f65e00fb798a079e40c153a0388f1ecb326a45bf
author Kevin McNee <mcnee@chromium.org> 1644355310 +0000
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> 1644355310 +0000

Don't iterate RenderFrameHosts when the WebContents is being destroyed

During WebContents destruction, its main RFH becomes null. Attempting
to iterate over RenderFrameHosts after that point would lead to a
crash.

We also remove part of a unit test that was simulating behaviour that
we're now asserting can't happen (hiding a WebContents that's being
destroyed).

Bug: 1290465
Change-Id: I91882d918146c463d7b3ff5493af6e7d60a5ca89
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3415711
Reviewed-by: Scott Violet <sky@chromium.org>
Reviewed-by: Charles Reis <creis@chromium.org>
Commit-Queue: Kevin McNee <mcnee@chromium.org>
Cr-Commit-Position: refs/heads/main@{#968548}