Interesting gotcha.  If you try to do these steps, *without* using a real server name(in place of the $server)), then the bug actually happens much more simply.  I get an error, name not resolved, and after the reload, the code continues to run.

This bug does *not* happen when the file is local, accessed via file:.  Only if it's on a remote server.

So, now I don't even need an example server to connect to.  Place the attached file on *any* remote server.  Start the loop(by clicking, but the loop could be started automatically), then hit reload/ctrl-r.

I was going to attach an example express-based server, but then noticed it wasn't even needed.

Interesting. Are you able to replicate this issue in a current version of Chrome (e.g. Chrome 62+)?

I don't think this is V8-related. To me it sounds like this is something the embedder (blink) should handle.

I just upgraded a windows machine to: Version 62.0.3202.89 (Official Build) (64-bit)

My debian system has over 100 tabs(in various windows), so upgrading that is difficult(I'm in the middle of website development).

The bug still occurs in 62, on windows, and 60, on linux.

Thank you for providing more feedback. Adding requester "elawrence@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Firefox 45 does not have this problem.  A reload stops the the background code.

In reproducing this, I find that the requests continue if I reload the page or perform a same-origin navigation. However, if I navigate to a foreign page (either on a different host, or about:blank), the background requests stop. 

Have you found a way to keep the requests going when that's not the case? If not, then the security implications of this seem especially mild (since the current page in the domain could simply continue issuing the requests directly). 

Tentatively triaging as low severity, though it's not clear to me that there are meaningful security implications. tyoshino, could you please take a look and see if you can suggest an appropriate owner?

I can confirm that browsing from my test server seems to stop the background.  I was also trying to make a setInterval(busyLoop) thing, but I have to switch back to real work for end-of-day.  I can try poking a bit more tomorrow, but this does appear limited to $currentDomain.

Yutaka, could you please take a look?

Is this dup of  issue 726302 ?

RE #13: Yes, it looks like a duplicate to me.

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot