Chrome Version: 57.0.2980.0 (trunk build)
OS: Linux

This bug was first discovered in a test for Iframes inside of devtools extensions in '--isolate-extensions' mode.  The bug seems to occur whenever the two subframes are in a different process than their parent, and both subframes are navigated to the same URL.

Steps to reproduce the problem:
(1) Start chrome in '--site-per-process' mode.
(2) Navigate to "dual_iframes_test.html" (attached).
(3) The page will contain two IFrames, each with an accompanying button.  Name either one Frame A and Frame B.
(4) Click on Frame A's button, which navigates to dudeguy409.github.io.
(5) Open chrome task manager (shift+esc) and end the process "dudeguy409.github.io".
(6) Click repeatedly on Frame B's button, and cry.
(7) Click on Frame A's button again, reloading the IFrame.
(8) Click repeatedly on Frame B's button again, and cry again.
(9) (Re)Open chrome task manager (shift+esc) and end the process "dudeguy409.github.io" again.
(10) Click on Frame B's button again, and cheer.

It should be noted that this issue doesn't occur at all if both buttons are clicked before killing the subframe process.


What is the expected result?
Frame B should load successfully in steps 6 and 8.

What happens instead?
Doesn't seem to do anything. The loading Icon spins very briefly, then stops.


 

Deleted: dual.css 54 bytes

dual.css 54 bytes View Download

Deleted: dual_iframes_test.html 522 bytes

dual_iframes_test.html 522 bytes View Download

Deleted: dualscript.js 338 bytes

dualscript.js 338 bytes View Download