New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 689733 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Out until 24 Jan
Closed: Aug 8
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

[Renderer kill] RFH_CAN_COMMIT_URL_BLOCKED when trying to load CWS in iframe without network connectivity

Project Member Reported by alex...@chromium.org, Feb 7 2017

Issue description

What steps will reproduce the problem?
(1) Visit http://csreis.github.io/tests/cross-site-iframe.html.
(2) Disconnect the network.
(3) In DevTools, run: navFrame("https://chrome.google.com/webstore")

What is the expected result?
The network error page loads in the subframe.

What happens instead?
The top-level renderer is killed.  This is because the error page tries to commit in the parent frame's process while using the Chrome Web Store URL as the last committed URL, and so that process is killed by the CWS CanCommitURL check in RenderFrameHostImpl::OnDidCommitProvisionalLoad.

Note that for CWS, this happens regardless of any OOPIF modes.  Once we start locking down URLs and origins that can commit with OOPIF modes, we'll likely hit this more widely.  This is another manifestation of our well-known problems with error pages, similar to issues  622385  and 560511.
 
Project Member

Comment 1 by sheriffbot@chromium.org, Feb 12 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: -nasko@chromium.org
Labels: -Hotlist-Recharge-Cold
Owner: nasko@chromium.org
Nasko, can you check if this is something that we still need to do?  Seems that error page isolation for subframes should fix this?
FYI: This issue does no more reproduce. The error page is correctly displayed.
Status: Fixed (was: Untriaged)
Thanks for checking-- I'll mark it fixed.

Sign in to add a comment